From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: David Malcolm <dmalcolm@redhat.com>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>,
Thomas Koenig <tkoenig@netcologne.de>,
gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: Error when accessing git read-only archive
Date: Wed, 15 Sep 2021 15:37:10 +0200 [thread overview]
Message-ID: <20210915133710.agtw4l4vwjo6myhm@lug-owl.de> (raw)
In-Reply-To: <3d642e058b5fde27ec3dd955183a3b2de934174c.camel@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1560 bytes --]
Hi David, Jonathan and all others,
On Wed, 2021-09-15 09:21:04 -0400, David Malcolm via Gcc <gcc@gcc.gnu.org> wrote:
> On Mon, 2021-09-13 at 14:03 +0100, Jonathan Wakely via Gcc wrote:
> > On Mon, 13 Sept 2021 at 14:01, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> > > On Mon, 13 Sept 2021 at 13:53, Thomas Koenig via Gcc <gcc@gcc.gnu.org> wrote:
>
> Summarizing some notes from IRC:
>
> The last commit it manages to print successfully in that log seems to
> be:
> c012297c9d5dfb177adf1423bdd05e5f4b87e5ec
> so it appears that:
> 42e95a830ab48e59389065ce79a013a519646f1
> is triggering the issue, and indeed
> https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=f42e95a830ab48e59389065ce79a013a519646f1
> fails in a similar way, whereas other commits work.
>
> It appears to be due to the "ł" character in the email address of the
> Author, in that:
>
> commit c012297c9d5dfb177adf1423bdd05e5f4b87e5ec
> Author: Jan-Benedict Glaw <jbglaw@lug-owl.de>
>
> works, whereas:
>
> commit f42e95a830ab48e59389065ce79a013a519646f1
> Author: Jan-Benedict Glaw <jbglaw@ług-owl.de>
That was indeed me, after moving my GCC repo to a different machine
and adding an explicit user.email (as this wasn't automatically
picking up a proper domain.) The "ł" was a typo (AltGr key still
pressed while typing the "l" after having entered the "@" which
requires it on a German keyboard layout.)
So I broke it. Any way to make sure something like this doesn't
occur again?
Sorry for inconvenience!
Jan-Benedict
--
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2021-09-15 13:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 12:52 Thomas Koenig
2021-09-13 13:01 ` Jonathan Wakely
2021-09-13 13:03 ` Jonathan Wakely
2021-09-15 13:18 ` Jonathan Wakely
2021-09-15 13:21 ` David Malcolm
2021-09-15 13:37 ` Jan-Benedict Glaw [this message]
2021-09-15 13:43 ` Jonathan Wakely
2021-09-15 14:10 ` Mark Wielaard
2021-09-15 18:34 ` Jan-Benedict Glaw
2021-09-15 14:14 ` Jan-Benedict Glaw
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=20210915133710.agtw4l4vwjo6myhm@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=dmalcolm@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=tkoenig@netcologne.de \
/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).