On Mon, Sep 10, 2007 at 11:06:18AM +0000, Wincent Colaiuta wrote:
> Admittedly, I try to avoid these things by not giving my files names like
> "master" or creating tags like "v1.0.0" and then adding files with the
> same name, but it would be nice for beginning users if you didn't have to
> think about this class of potential ambiguities.
Nope you definitely can have a file named master, actually at work we
have a directory of our repository called master. But a refname / path
ambiguity is easy to solve in git: add '--' before if it's a path, or
after the token if you mean the reference, and all is fine.
Unlike branch/tag ambiguity that is heavy to resolve (you have to
prepend refs/{tags,heads}/ which is very long and "complex" to type)
disambiguate a path is easy and straightforward. My point is that
reference/path ambiguity is easy to deal with even from a beginner PoV.
--
·O· Pierre Habouzit
··O madcoder@xxxxxxxxxx
OOO http://www.madism.org
Attachment:
pgpgGqV9gpvDH.pgp
Description: PGP signature
