From: Cary Coutant <ccoutant@google.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Binutils <binutils@sourceware.org>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: small request regarding commits in binutils-gdb.git
Date: Wed, 15 Jan 2014 19:31:00 -0000 [thread overview]
Message-ID: <CAHACq4o_L+s_U2ew-2emAAKLFXYRrrVhc_ozeO3icynNNNYK1A@mail.gmail.com> (raw)
In-Reply-To: <20140115121251.GM4639@adacore.com>
> For the rest of the community, using a meaningful subject, one that
> actually gives a hint at what it does, is something that I have
> found to be really helpful. For instance, "Provide format string
> to as_warn" can be more helpful when scanning through a list
> of commits than "PR gas/16434".
This is all good, but could you clarify what the conventions are now
for where the "PR gas/16434" needs to go in order for the patch to get
sent to bugzilla?
-cary
next prev parent reply other threads:[~2014-01-15 19:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 12:12 Joel Brobecker
2014-01-15 15:28 ` Mike Frysinger
2014-01-15 15:51 ` Tom Tromey
2014-01-15 16:04 ` Eli Zaretskii
2014-01-15 16:25 ` Joel Brobecker
2014-01-15 16:57 ` Eli Zaretskii
2014-01-15 17:12 ` Mike Frysinger
2014-01-15 19:48 ` Fred Cooke
2014-01-15 20:02 ` Mike Frysinger
2014-01-15 20:38 ` Eli Zaretskii
2014-01-15 20:57 ` Mike Frysinger
2014-01-15 21:09 ` Eli Zaretskii
2014-01-16 2:11 ` Alan Modra
2014-01-16 2:17 ` Joel Brobecker
2014-01-16 1:41 ` Fred Cooke
2014-01-16 2:41 ` Mike Frysinger
2014-01-15 16:50 ` Pedro Alves
2014-01-15 17:03 ` Tom Tromey
2014-01-15 18:07 ` Gary Benson
2014-01-16 11:41 ` Jose E. Marchesi
2014-01-15 19:31 ` Cary Coutant [this message]
2014-01-15 19:45 ` Tom Tromey
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=CAHACq4o_L+s_U2ew-2emAAKLFXYRrrVhc_ozeO3icynNNNYK1A@mail.gmail.com \
--to=ccoutant@google.com \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.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).