From: "Martin Liška" <mliska@suse.cz>
To: Overseers mailing list <overseers@sourceware.org>,
GCC Development <gcc@gcc.gnu.org>
Subject: Re: Missing commit in gcc-cvs mailing list
Date: Wed, 7 Oct 2020 14:01:50 +0200 [thread overview]
Message-ID: <cdb38ade-5b65-7720-52fd-9b9074bdf3a1@suse.cz> (raw)
In-Reply-To: <d34e1e9e-cc50-da5d-15b0-d03d43c3aca0@suse.cz>
On 10/7/20 8:52 AM, Martin Liška via Overseers wrote:
> My commit 190c04ba36d9c6c3dce41f12012aa97c6d7f22f5 is missing in the
> mailing list (and so was not propagated to the corresponding PR):
> https://gcc.gnu.org/pipermail/gcc-cvs/2020-October/date.html
>
> There's previous and next commit:
> [gcc r11-3678] [PATCH][GCC] arm: Move iterators from mve.md to iterators.md to maintain consistency. SRINATH PARVATHANENI
> ... should be here ...
> [gcc r11-3680] [openacc] Fix acc declare for VLAs Tom de Vries
>
> Can please anybody check that?
> Thanks,
> Martin
I've got it. It's caused by fact that I copied a strange character to
the git commit message. My testing script fails for it as well:
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 954: ordinal not in range(128)
Martin
prev parent reply other threads:[~2020-10-07 12:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 6:52 Martin Liška
2020-10-07 12:01 ` Martin Liška [this message]
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=cdb38ade-5b65-7720-52fd-9b9074bdf3a1@suse.cz \
--to=mliska@suse.cz \
--cc=gcc@gcc.gnu.org \
--cc=overseers@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).