El 28/5/2008, a las 8:12, Junio C Hamano escribió:
Mark Levedahl <mlevedahl@xxxxxxxxx> writes:
As this commit is part of the published master branch, I am not sure
the correct resolution: leaving this commit in place means that any
commit between it and a commit fixing this will always cause an error
on Cygwin / Windows. Of course, it *is* on the published master
branch.
Some broken filesystems may not be capable of checking out and using
project files. Too bad.
It's not a big deal. It is not limited to this project. We just
fix them
or work them around and move on.
Perhaps we should remove the infamous gitweb/test/Märchen file while
we
are at it? I do not think the file is ever used.
I for one would love to see it go, seeing as I live in the ghetto that
is HFS+ and am constantly annoyed by it cluttering up my status output
with spurious content.
I understand that the reason it lives in the tree is precisely to
discover problems with such filesystems, but the problem is well and
truly discovered by now and I'd much rather see this kind of thing
tested from within the test suite rather than every time I do "git
status" or "git checkout".
Cheers,
Wincent
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
