From: Allan Caffee <allan.caffee@gmail.com>
Date: Sat, 30 Jul 2011 13:29:58 GMT
Subject: Re: Unusual behavior from git describe
Message-ID: <CA+jCPNfwwhM8R-bB_VnwpaijSMf3BNydH35SqZt3dRb-P1AOmg@mail.gmail.com>
In-Reply-To: <CAGdFq_hYiBoqNmNtBKBqNN4XLLKwxDMHJfAUwdHB_iCcya=DOQ@mail.gmail.com>

Hey,

On Fri, Jul 29, 2011 at 5:55 PM, Sverre Rabbelier <srabbelier@gmail.com> wrote:
> Heya,
>
> On Fri, Jul 29, 2011 at 23:46, Allan Caffee <allan.caffee@gmail.com> wrote:
>> % git describe --tags --dirty
>> v0.0.3-dirty
>>
>> % git status
>> # On branch master
>> nothing to commit (working directory clean)
>>
>> % git describe --tags --dirty
>> v0.0.3
>
> Perhaps git describe does not update the index (properly?), which 'git
> status' then does, correcting it?

I suppose that makes sense.  But what about building a package, which
doesn't change any tracked files or add any (non-ignored) untracked
files, would cause the index to appear dirty in the first place?

--
Allan