git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC] describe: add option --dirty

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 23, 2007, 06:56 UTC
Message-ID
<7vsl7fmwud.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<87odi3mxtl.wl@mail2.atmark-techno.com>
Yasushi SHOJI <yashi@atmark-techno.com> writes:
Show 5 quoted lines
> 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...

Previous: Yasushi SHOJINext: Shawn O. Pearce
Message 2 of 7 in “[RFC] describe: add option --dirty”
  1. Yasushi SHOJIJul 23, 2007
  2. Junio C HamanoJul 23, 2007
  3. Shawn O. PearceJul 23, 2007
  4. Yasushi SHOJIJul 23, 2007
  5. Shawn O. PearceJul 23, 2007
  6. Yasushi SHOJIJul 23, 2007
  7. Shawn O. PearceJul 23, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.