It seems you sent this bug report to bug-automake by bcc.
This confuses debbugs.gnu.org, which has no idea which package the
report should be associated with. Hence your message ended up on the
help-debbugs mailing list. I have assigned your report to automake, so
that this message and any future
Hi,
You change this by going to the "administrative interface" in mailman
https://lists.gnu.org/mailman/admin/automake
Then in the "General Options" page, edit the "introductory description"
section and then press "submit". Changes should be instantaneous.
[ This was sent to "bugs-autom...@gnu", apparently an alias for
"bug-automake". Because debbugs was unaware of this, it was assigned
to the default package, debbugs itself. I have reassigned it to
automake and am resending this so it goes to the right list.
The alias (along with "automake-bugs?" h
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
Ralf Wildenhues wrote (on Mon, 8 Nov 2010 at 22:46 +0100):
> > BTW, Ouch! I see that my previous reply presenting the patch
> > has erroneously opended a new, spurious bug report (#7345) in
> > the tracker! Ralf, could you please you close that report as
> > invalid?
>
> Not sure how that happ
