From: Simon Marchi <simon.marchi@polymtl.ca>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: Format of patterns recognized in commit messages for auto-posting in bugs
Date: Fri, 22 Apr 2022 13:49:17 -0400 [thread overview]
Message-ID: <67dd0291-2672-9bd4-3b11-877207d11f7f@polymtl.ca> (raw)
Hi Joel,
What are the formats recognized by the git hooks to detect that a commit
refers to a Bugzilla bug, and post a message on that bug? We used to
write "PR gdb/1234" and it was recognized. Now, we use "Bug:" trailers,
like in this commit:
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=152a17495663ae9099d5efdc38322c9ad348014e
... but it doesn't seem recognized. Would it be possible to recognize
Bugzilla URLs?
Simon
next reply other threads:[~2022-04-22 17:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 17:49 Simon Marchi [this message]
2022-04-22 18:11 ` Joel Brobecker
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=67dd0291-2672-9bd4-3b11-877207d11f7f@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=brobecker@adacore.com \
--cc=gdb@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).