From: "Martin Liška" <mliska@suse.cz>
To: Uros Bizjak <ubizjak@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: git commit hook does not record my patches to PRs
Date: Wed, 6 Jan 2021 10:53:19 +0100 [thread overview]
Message-ID: <d0607ed6-4ea9-eac0-b00a-0bb71542d2d3@suse.cz> (raw)
In-Reply-To: <CAFULd4ZpOF=r4pQp9kYbVHW3W46s_dK+K8JZrUGbOV9Qfx1vGw@mail.gmail.com>
On 1/5/21 3:04 PM, Uros Bizjak wrote:
> Hello!
>
> For some reason git commit hook does not record my patches to PRs,
> mentioned in the commit message. Some recent examples:
>
> PR 98521:
> https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=951bdbde6ade56eb63af1dfa18777348a8a0d89e
>
> and PR98522:
> https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=1ff0ddcd8b4728bcc96e1daf2e70a03dc9fbf171
>
> These two patches were committed as a single push (but one commit per
> push also doesn't reach the PR), and the second one is also missing in
> the gcc-cvs mailing list archive:
>
> https://gcc.gnu.org/pipermail/gcc-cvs/2021-January/date.html
>
> In the commit message, I have put PR marks everywhere I can think of,
> but the commit hook is still ignoring them. Can someone please check,
> what is wrong with the flow and eventually advise me what to do to
> enjoy the benefits of the automation.
Hello.
I can reproduce that for gcc-reposurgeon-8 repository and yes, it's again related
to a unicode characters (in your case 'š' letter in your first name).
I'll debug that with Jakub.
Martin
>
> Thanks,
> Uros.
>
next prev parent reply other threads:[~2021-01-06 9:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 14:04 Uros Bizjak
2021-01-05 14:07 ` Jakub Jelinek
2021-01-06 9:53 ` Martin Liška [this message]
2021-01-06 13:46 ` Martin Liška
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=d0607ed6-4ea9-eac0-b00a-0bb71542d2d3@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@gcc.gnu.org \
--cc=ubizjak@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).