From: "Martin Liška" <mliska@suse.cz>
To: Gerald Pfeifer <gerald@pfeifer.com>, NightStrike <nightstrike@gmail.com>
Cc: Jonathan Yong <10walls@gmail.com>,
i.nixman@autistici.org, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: realpath() patch to fix symlinks resolution for win32
Date: Mon, 13 Feb 2023 13:03:41 +0100 [thread overview]
Message-ID: <0fbac9f2-f533-a97b-8516-e40d8f9d01c9@suse.cz> (raw)
In-Reply-To: <da005c26-9a88-b0bb-edb0-a4509aca6db1@pfeifer.com>
On 2/11/23 22:14, Gerald Pfeifer wrote:
> On Sat, 11 Feb 2023, NightStrike wrote:
>>>>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108350
>> I would have expected the PR to have been automatically updated based on
>> the commit email. Any idea why that didn't happen? Not to change the state
>> to closed, but to add the commit information as a reply.
>
> I assume the fact that the PR reference was spelt as
> PR/108350
> without a slash, not a blank, after "PR" may be responsible for the
> missing Bugzilla comment.
>
> The documented format - per gcc.gnu.org/codingconventions.html - is
> PR component/12345
It's likely what happens.
>
> Martin? (By the way, where does one best have a look at those hooks?
> .git/hooks in the main repository isn't it, it appears?)
I know that server hooks (gcc.gnu.org:/home/gccadmin/hooks-bin) do contain:
email-to-bugzilla-filtered:BUGZILLA_CMD = ("/sourceware/infra/bin/email-to-bugzilla", "-G", "gcc")
thus I guess it's /sourceware/infra/bin/email-to-bugzilla what makes the filtering of commits
to bugzilla.
Martin
>
> Gerald
next prev parent reply other threads:[~2023-02-13 12:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 10:44 i.nixman
2023-02-06 6:40 ` Jonathan Yong
2023-02-11 6:32 ` Jonathan Yong
2023-02-11 7:28 ` i.nixman
2023-02-11 8:36 ` Jonathan Yong
2023-02-11 8:52 ` Gerald Pfeifer
2023-02-11 13:24 ` Jonathan Yong
2023-02-11 18:00 ` NightStrike
2023-02-11 21:14 ` Gerald Pfeifer
2023-02-13 12:03 ` Martin Liška [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-26 17:51 i.nixman
2023-01-16 17:06 i.nixman
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=0fbac9f2-f533-a97b-8516-e40d8f9d01c9@suse.cz \
--to=mliska@suse.cz \
--cc=10walls@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=i.nixman@autistici.org \
--cc=nightstrike@gmail.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).