From: Johannes Schindelin Date: Tue, 19 Jan 2010 10:35:41 GMT Subject: Re: git-describe recognize modified files Message-ID: In-Reply-To: <829260.92036.qm@web45202.mail.sp1.yahoo.com> Hi, On Tue, 19 Jan 2010, tzachi perelstein wrote: > 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