From: Hans-Peter Nilsson <hp@bitrange.com>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: gcc-patches@gcc.gnu.org, <gcc@gcc.gnu.org>
Subject: Re: Starting to track patches through bugzilla
Date: Sat, 27 Sep 2003 10:24:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.44.0309270147210.43003-100000@dair.pair.com> (raw)
In-Reply-To: <2818635A-EF7E-11D7-9657-000A95AF1FAE@dberlin.org>
Great.
On Thu, 25 Sep 2003, Daniel Berlin wrote:
> Userids it can't determine (due to non-existent bugzilla accounts or
> not writing from the same email address you use in your bugzilla mail)
> are currently set to me, rather than creating them new accounts. It'll
> likely just be set to an "unknown commenter" account with the from
> pasted into the text of their followup.
I don't want to send patches from hp gcc gnu org but I want to
be that my "official" bugzilla account. Can I make that and
this addresses aliases (and more addresses)?
> An example of this theory is that patches with subjects not starting
> with [PATCH] don't get processed (and any followup referencing them
> won't get processed as a result). This is good enough, since people
> are supposed to do it. Patches that don't do it have the same chance as
> before of being lost in the ether.
Please also [RFA] and [RFA:] (request for approval) as the
convention is, as was suggested last time this came up. (Maybe
RFC too, but IMHO that's a misnomer.)
brgds, H-P
next prev parent reply other threads:[~2003-09-27 5:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-25 18:12 Daniel Berlin
2003-09-25 21:16 ` Daniel Berlin
2003-09-26 0:21 ` Carlo Wood
2003-09-26 0:26 ` Daniel Berlin
2003-09-26 2:09 ` Tom Tromey
2003-09-27 10:24 ` Hans-Peter Nilsson [this message]
2003-09-27 17:02 ` Daniel Berlin
2003-09-27 17:15 ` Hans-Peter Nilsson
2003-09-27 19:15 ` Daniel Berlin
2003-09-27 20:27 ` Hans-Peter Nilsson
2003-09-27 21:02 ` Daniel Berlin
2003-09-27 22:14 ` Hans-Peter Nilsson
2003-09-27 22:18 ` Daniel Berlin
2003-09-27 17:05 ` Jeff Sturm
2003-09-27 17:45 ` Hans-Peter Nilsson
2003-10-01 18:59 ` Gerald Pfeifer
2003-09-26 6:50 Nathanael Nerode
2003-09-27 0:03 ` Joseph S. Myers
2003-09-27 0:22 ` Daniel Berlin
2003-09-27 1:57 ` Gabriel Dos Reis
2003-09-27 3:26 ` Daniel Berlin
2003-09-27 5:52 ` Gabriel Dos Reis
2003-09-27 9:43 ` Tom Tromey
2003-10-01 20:51 Wolfgang Bangerth
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=Pine.BSF.4.44.0309270147210.43003-100000@dair.pair.com \
--to=hp@bitrange.com \
--cc=dberlin@dberlin.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
/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).