On Apr 18, 2008, at 8:09 AM, Steffen Prohaska wrote:
On Thu, 17 Apr 2008, Junio C Hamano wrote:
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.
I continue to merge Junio's next from time to time and push it to
4msysgit. Quite a few tests currently fail, so it could be a good idea
to have a closer look. Now we have a chance of fixing problems
upstream, such that Junio's master directly works on Windows.
Steffen
