From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Martin Sebor <msebor@gmail.com>
Cc: Marek Polacek <polacek@redhat.com>, gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: where is PRnnnn required again?
Date: Wed, 7 Jul 2021 23:24:56 +0100 [thread overview]
Message-ID: <CAH6eHdQe4t=_HDrnDZj+gqy9bWVZNtaF7ZLYJ88QgV=AjSPfhQ@mail.gmail.com> (raw)
In-Reply-To: <734e36bd-5adb-feed-7e89-d63d233198a4@gmail.com>
On Wed, 7 Jul 2021, 23:18 Martin Sebor, <msebor@gmail.com> wrote:
> On 7/7/21 3:53 PM, Marek Polacek wrote:
> > I'm not sure why you keep hitting so many issues; git addlog takes care
> of
> > this stuff for me and I've had no trouble pushing my patches. Is there
> > a reason you don't use it also?
>
> I probably have a completely different workflow. Git addlog isn't
> a git command (is it some sort of a GCC extension?), and what I put
> in the subject of my emails is almost never the same thing as what
> I put in the commit message.
Why not? Why is it useful to write two different explanations of the patch?
next prev parent reply other threads:[~2021-07-07 22:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 21:20 Martin Sebor
2021-07-06 21:36 ` Marek Polacek
2021-07-06 21:44 ` Martin Sebor
2021-07-06 22:09 ` Jonathan Wakely
2021-07-07 16:39 ` Martin Sebor
2021-07-07 20:42 ` Jonathan Wakely
2021-07-07 21:35 ` Martin Sebor
2021-07-07 21:53 ` Marek Polacek
2021-07-07 22:18 ` Martin Sebor
2021-07-07 22:24 ` Jonathan Wakely [this message]
2021-07-07 22:58 ` Martin Sebor
2021-07-07 23:03 ` David Malcolm
2021-07-08 8:26 ` Jonathan Wakely
2021-07-08 18:58 ` Martin Sebor
2021-07-07 22:15 ` Jonathan Wakely
2021-07-07 23:38 ` Martin Sebor
2021-07-07 17:51 ` Jakub Jelinek
2021-07-07 19:01 ` Martin Sebor
2021-07-07 21:01 ` Jason Merrill
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='CAH6eHdQe4t=_HDrnDZj+gqy9bWVZNtaF7ZLYJ88QgV=AjSPfhQ@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=msebor@gmail.com \
--cc=polacek@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).