Repository navigation
Forking mgwport #17
Description
Activity
I'd be in favor of forking into
git-for-windows... Then you could also incorporate yourmpfeatures...Okay, so I'll move it to git-for-windows as @sschuberth was also in favour of that.
Done, see https://github.com/git-for-windows/mgwport.
- added 2 commits that reference this issue
on Mar 10, 2021 - added a commit that references this issue
on Apr 12, 2021 - added 2 commits that reference this issue
on Apr 28, 2021 - added 2 commits that reference this issue
on Jun 11, 2021 27 remaining items
- added a commit that references this issue
on Dec 31, 2024 - added a commit that references this issue
on Aug 13, 2025 - added 2 commits that reference this issue
on Dec 9, 2025 - added 2 commits that reference this issue
on Dec 11, 2025 - added 2 commits that reference this issue
on Jan 8, 2026 - added a commit that references this issue
on Jan 29, 2026 - added a commit that references this issue
on Sep 14, 2026
Metadata
Metadata
Assignees
Labels
No labels
Upstream mgwport is dead, last update from Friday, November 11 2011, I've tried to email the author no answer.
For the deterministic build changes I need to therefore create a new package mingw32-mgwport.
Do we want to have mgwport in git-for-windows org or should I keep it in t-b? For me both is okay.