On Thu, 17 Apr 2008, Junio C Hamano wrote:
> Steffen Prohaska <[EMAIL PROTECTED]> writes:
>
> > The patches are not included in 1.5.5. The patch series by Linus
> > (tip is 1102952b4) is on Junio's next branch, so I guess it will
> > become available in Git 1.5.6.
>
> Because I do not use Windows for development myself, unless and until I
> hear from people who have exercised the code and ironed out the kinks on
> Windows, either:
Unfortunately, the same is true for me. I maintain msysgit only because
I need to provide a Git working environment for some colleagues;
otherwise they would not allow me to use Git on Mac OS X and Linux.
>
> (1) The series does not graduate to 'master' by the time 1.5.6 happens,
> because the series is unnecessary on POSIX systems; and/or
>
> (2) It is included in 1.5.6, but what I can guarantee stops at "this does
> not hurt POSIX systems when it is not activated". IOW, if activated,
> it may not work on Windows at all.
Mac OS X also has a case insensitive file system. Thus, the series
should receive some testing, even if it is not yet available on Windows.
>
> How would you guys want to proceed from here?
Merge all modifications that we have in msysgit to your master, such
that we can build the Windows release directly from your repository ;-)
Then, the Windows people could directly test your next. Unfortunately,
I do not think that this is realistic now.
So maybe we can do what I noted below ...
>
> If msysgit people can try it out and resolve potential issues while it is
> still on 'next' in my tree, we can have a 'tested and seems to work even
> on Windows' version in 'master' when the series is included in a tagged
> release of git, perhaps in 1.5.6 or 1.6.0.
>
>
[...]
>
> IOW, there should be more "that series on 'next' needs to be updated with
> these patches to work on Windows, please do not merge them to 'master'
> before the issue is resolved", and less "the newly released git, which
> contains this and that features that have been cooking for a few weeks on
> 'next' that have recently graduated to 'master', do not work on Windows".
I could regularly publish a "next" branch in 4msysgit that tracks Junio's
next branch and has the same reset policy. 4msysgit's "next" branch
would be reset to master after the end of a release cycle. I would
merge Junio's next and verify that it compiles. I would not, however,
do any further testing before pushing. This would be up to the
community.
To see if this is practical, I merged Junio's current next and pushed it to
4msysgit. The tip is "c0f08f53".
>
> The latter is a sure sign that the Windows people are not participating
> enough (and I think you know which change in 1.5.5 I am talking about).
>
Yes.
Steffen
