Yasushi SHOJI <yashi@xxxxxxxxxxxxxxxxx> writes:
> when --dirty is given, git describe will check the working tree and
> append "-dirty" to describe string if the tree is dirty.
> ---
> I'm not sure this is good idea or the current way (using diff-index in
> shell script) is more prefered.
Hmph, this makes sense _ONLY_ for HEAD, doesn't it?
IOW, what should this output?
$ git checkout v1.5.0 ;# detached HEAD
$ git reset --hard ;# clean slate
$ echo >>Makefile ;# not anymore
$ git describe --dirty v1.4.0^1
Should it say "v1.4.0-rc2-156-g0a8f4f0-dirty"? The dirtiness
does not have anything to do with commit v1.4.0^1, so...
-
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
