Repository navigation
Forking mgwport #17
Description
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.
Metadata
Metadata
Assignees
Labels
No labels
Activity
dscho commentedon Oct 17, 2014
I'd be in favor of forking into
git-for-windows... Then you could also incorporate yourmpfeatures...t-b commentedon Oct 23, 2014
Okay, so I'll move it to git-for-windows as @sschuberth was also in favour of that.
t-b commentedon Nov 13, 2014
Done, see https://github.com/git-for-windows/mgwport.
init: remove git_init_db_config() while fixing leaks
init: remove git_init_db_config() while fixing leaks
builtin/checkout: clear pending objects after diffing
revision: free remainder of old commit list in limit_list
builtin/checkout: clear pending objects after diffing
bulk-checkin: make buffer reuse more obvious and safer
split-index: use oideq instead of memcmp to compare object_id's
27 remaining items
bulk-checkin: fix segfault with unsafe SHA1 backend
Fix rare segfault in sparse-index (git-for-windows#690)
Fix rare segfault in sparse-index (git-for-windows#690)
Fix rare segfault in sparse-index (git-for-windows#690)
Fix rare segfault in sparse-index (git-for-windows#690)
Fix rare segfault in sparse-index (#690)
builtin/gc: fix condition for whether to write commit graphs
odb: properly close sources before freeing them
builtin/gc: fix condition for whether to write commit graphs
odb: properly close sources before freeing them
Fix rare segfault in sparse-index (git-for-windows#690)
builtin/gc: fix condition for whether to write commit graphs
odb: properly close sources before freeing them
Fix rare segfault in sparse-index (#690)
builtin/history: unuse the commit buffer after use