* Glenn Morris wrote on Wed, Nov 10, 2010 at 09:46:01PM CET:
>
> Actually, that was probably too glib a response. The version number
> information is probably used in other places, and needs to be sortable
> so that the fixed/found commands can work. So I don't think arbitrary
> version strings ca
Actually, that was probably too glib a response. The version number
information is probably used in other places, and needs to be sortable
so that the fixed/found commands can work. So I don't think arbitrary
version strings can work. You could use the date of a commit perhaps.
Ralf Wildenhues wrote:
> Can that be fixed in debbugs? I would love to have both 'git describe'
> output as well as commit SHA1 strings be acceptable as version strings.
> git describe output starts with v but then contrains fairly much
> arbitrary characters as put in the last signed git tag. S
* Glenn Morris wrote on Tue, Nov 09, 2010 at 08:34:23AM CET:
> Ralf Wildenhues wrote (on Mon, 8 Nov 2010 at 22:46 +0100):
> > The commands above (Bcc:ed to control at debbugs) should merge and
> > close both bugs.
>
> The (first) close didn't work, I think it was because your version
> number star
