From: "H.J. Lu" <hjl.tools@gmail.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: Please put binutils PR number in git commit log
Date: Mon, 17 Feb 2020 15:47:00 -0000 [thread overview]
Message-ID: <CAMe9rOoaUZNNj1L0O=QS1vUMa2FZGw-n1rfg-w8vSKzLYfZu6w@mail.gmail.com> (raw)
In-Reply-To: <c87f007a-1e31-389a-d25c-2c1dfe27d7e1@suse.com>
On Mon, Feb 17, 2020 at 7:43 AM Jan Beulich <jbeulich@suse.com> wrote:
>
> On 17.02.2020 16:41, H.J. Lu wrote:
> > On Mon, Feb 17, 2020 at 7:31 AM Jan Beulich <jbeulich@suse.com> wrote:
> >>
> >> On 17.02.2020 15:52, H.J. Lu wrote:
> >>> Please put put binutils PR number in git commit log, like
> >>>
> >>> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=0aa99dcd70bce68f8efef310350a6294e1143382
> >>>
> >>> so that the bug report which the patch is fixing will be updated automatically.
> >>
> >> I was wondering how this auto-updating works. But repeating the ChangeLog
> >> entries in the commit message is not an option imo. Or is this spelled
> >> out as a requirement somewhere? There should be a way to achieve this
> >> without such redundancy.
> >>
> >
> > This is how git commit updates bug report today. Until it is changed, please
> > add PR number in git commit log.
>
> I'm happy to do so, but not in the shape you've pointed at as an
> example. What exactly is being looked for by whatever grabs the
> number out of the description?
I think "PR component/number" works in subject or the message body.
--
H.J.
next prev parent reply other threads:[~2020-02-17 15:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMe9rOpbgvJ1h=fQkguX6bPDJxMkNMUSAd27RVUSZjXzz9WSwg@mail.gmail.com>
2020-02-17 15:31 ` Jan Beulich
2020-02-17 15:41 ` H.J. Lu
2020-02-17 15:43 ` Jan Beulich
2020-02-17 15:47 ` H.J. Lu [this message]
2020-02-17 15:50 ` Jan Beulich
2020-02-17 16:54 ` H.J. Lu
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='CAMe9rOoaUZNNj1L0O=QS1vUMa2FZGw-n1rfg-w8vSKzLYfZu6w@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.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).