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

Re: git-describe recognize modified files

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jan 19, 2010, 10:35 UTC
Message-ID
<alpine.DEB.1.00.1001191134130.3164@intel-tinevez-2-302>
In-Reply-To
<829260.92036.qm@web45202.mail.sp1.yahoo.com>
Hi,
On Tue, 19 Jan 2010, tzachi perelstein wrote:
Show 9 quoted lines
> I use git-describe to form a build version automatically. This allows me
> to deliver temporary builds for testing without having to make manual
> tags for them. The only thing that bothers me about this is that from
> the output of git-describe I cannot tell if there are some modified
> files in tree or not. In both cases I will get the same version. 
> 
> To solve this issue, in addition to git-describe, my do_version script
> also run git-status, and if there are "modified:" files then it
> concatenates the string "+dirty" to output of git-describe.

The problem is that this does not describe the exact version you used very well. If you are really serious about describing the exact state you described, make a tag (committing the changes to a detached HEAD first, if you do not want the changes in a real branch).

Ciao, Dscho

Previous: tzachi perelsteinNext: Andreas Krey
Message 2 of 6 in “git-describe recognize modified files”
  1. tzachi perelsteinJan 19, 2010
  2. Johannes SchindelinJan 19, 2010
  3. Andreas KreyJan 19, 2010
  4. Jakub NarebskiJan 19, 2010
  5. tzachi perelsteinJan 19, 2010
  6. tzachi perelsteinJan 19, 2010

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.