Re: [msysGit] How to reduce remaining differences to 4msysgit? (was What's cooking in git.git (topics))

On Montag, 30. Juni 2008, Steffen Prohaska wrote:

On Jun 30, 2008, at 11:08 AM, Junio C Hamano wrote:

quoted

* MinGW will be in.

If this is done, we should be able to create the msysgit release
directly
from Junio's master.  Hannes changes alone, however, are not sufficient,
because some commits have been parked in 4msysgit.  Now that MinGW is
on Junio's next and Junio's next is also on 4msysgit's next, it it easy
to see how much is left to do by running:

    git diff --stat junio/next..4msysgit/next

junio is a remote pointing to git://git.kernel.org/pub/scm/git/git.git.
4msysgit is a remote pointing to git://repo.or.cz/git/mingw/
4msysgit.git.
I attached the output below.

How should we proceed to get rid of the differences?

Should we prepare and send patches directly to the official git list
now?
Should we wait until the first MinGW branch is on master?
Should we prepare a whole patch series?  Maybe Hannes would maintain
this
patch series.

Until 1.6.0 is released, a number of _required_ patches will have to be 
included. There are two sorts of them:

* Patches that touch generic code, like replacing c == '/' by is_dir_sep(c).

* Patches that are purly Windows specific.

The former I intend to submit to the mailing list directly and as soon as 
possible (but if I can intervene on newly submitted patches early so that a 
fixup is not even necessary, then even better). The latter I intend to 
collect in a branch and submit as a batch. Let's see how this works out.

Then there are the extra patches in 4msysgit. From my POV, they are not 
_required_ because I can appearently work with git on Windows without them. I 
think some of them are not necessary. Can we go through them again?

And then there are the patches to the t/ directory. I do not target them for 
1.6.0, but I do want to prepare another series with them.

-- Hannes