From: Petter Reinholdtsen <pere@hungry.com>
To: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Fix PRs glibc/{93,94,98,107}
Date: Wed, 21 Apr 2004 22:39:00 -0000 [thread overview]
Message-ID: <20040421222215.GC12640@saruman.uio.no> (raw)
In-Reply-To: <200404211902.i3LJ2iao005165@magilla.sf.frob.com>
[Roland McGrath]
>> Selected obvious fixes from glibc bugzilla.
> I think we should start a convention for mentioning bug #s in log
> entries. Some rigid format that regexps can match easily.
I agree. Ulrich used "[BZ #19]" in a changelog entry, so I used the
same format.
> I think we can then set something up so the commits with matching
> entries automagically add comments to bugzilla.
That would be very good. :)
prev parent reply other threads:[~2004-04-21 22:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-21 12:35 Jakub Jelinek
2004-04-21 18:58 ` Ulrich Drepper
2004-04-21 19:02 ` Roland McGrath
2004-04-21 22:39 ` Petter Reinholdtsen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040421222215.GC12640@saruman.uio.no \
--to=pere@hungry.com \
--cc=libc-hacker@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).