bug#7333: [PATCH] {maint} Fix a bug in variable concatanation with `+='.

2010-11-10 Thread Ralf Wildenhues 
* 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 started with a `v', not a digit. The second close worked.

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.  SHA1's are
easier, and if the other is a problem then those would still be better
than no version information, I guess.

Thanks,
Ralf

bug#7333: [PATCH] {maint} Fix a bug in variable concatanation with `+='.

2010-11-10 Thread Glenn Morris 

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.

bug#7333: [PATCH] {maint} Fix a bug in variable concatanation with `+='.

2010-11-10 Thread Ralf Wildenhues 
* 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 can work. You could use the date of a commit perhaps.

If that's the case, let's I'd say just live with it.  Anyway better to
send mail to NNN-done, where one can include arbitrary detail.

Thanks for checking,
Ralf