El 17/1/2008, a las 12:10, Johannes Schindelin escribió:
On Thu, 17 Jan 2008, Wincent Colaiuta wrote:
And what do we do when asked to check out a tree which has two
different
files in it whose normalized forms are the same (ie. a clone of a
repo
created on a non-HFS+ filesystem)?
We either have to fail catastrophically, preventing the user from
working with that tree on HFS+, or arbitrarily pick one of the
files as
the "winner" which gets written out into the work tree. None of the
options is particularly attractive, although luckily this exact
situation is unlikely to come up in practice.
Anything else but failure would be Not What You Want. You might
want a
special mode where you use a _different_ name on-disk (something
like the
infamous short names on FAT), but that _must_ be turned off by
default:
think of Martin's HEAD example. Sometimes, it's just not possible to
check such a tree out on a less-than-nice system.
Such a special mode would be mostly useless in most contexts, where
Git is used to track source code. It would enable you to check out the
tree for inspection, but you probably couldn't build anything from it
seeing as at least one of the filenames specified in your Makefile
wouldn't be present in the work tree.
As such, in that kind of situation I'd rather see a big red warning
printed out that the checkout failed because a particular file
couldn't be written out, and perhaps an instruction to the user that
they can use "git show" if they want to see the blob/s which wasn't/
weren't written.
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
