From: Jakub Jelinek <jakub@redhat.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: Ian Lance Taylor <iant@golang.org>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Jonathan Wakely <jwakely.gcc@gmail.com>
Subject: Re: Patch RFA: Support non-ASCII file names in git-changelog
Date: Mon, 21 Dec 2020 10:48:37 +0100 [thread overview]
Message-ID: <20201221094837.GG3788@tucnak> (raw)
In-Reply-To: <733ffec8-8809-d7fd-f0bf-9b1d9a55d7fc@suse.cz>
On Mon, Dec 21, 2020 at 10:39:31AM +0100, Martin Liška wrote:
> On 12/18/20 7:30 PM, Ian Lance Taylor wrote:
> > I don't know the tradeoffs here. This approach sounds fine to me.
>
> Trade off is that we need to setup server (that's fine).
> And people have to locally do the same, otherwise they'll newly see:
>
> $ git gcc-verify -p
> Checking 6c439cadf0362cc0f8f2b894c1b596bbf822849b: FAILED
> ERR: Quoted UTF8 filename, please set: "git config --global core.quotepath false":""kon\303\255\304\215ek.txt""
>
> @Jakub: Can you please update the server hook (git_commit.py) file and set:
>
> git config --global core.quotepath false
>
> for the user that runs the server hooks?
I have no idea who that is (if it is a single user at all,
if it isn't any user with git write permissions).
Jakub
next prev parent reply other threads:[~2020-12-21 9:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 4:26 Ian Lance Taylor
2020-12-18 10:28 ` Martin Liška
2020-12-18 18:30 ` Ian Lance Taylor
2020-12-21 9:39 ` Martin Liška
2020-12-21 9:48 ` Jakub Jelinek [this message]
2020-12-21 9:57 ` Martin Liška
2020-12-24 12:16 ` Joel Brobecker
2021-01-04 11:01 ` Martin Liška
2021-01-04 11:47 ` Martin Liška
2021-01-06 7:25 ` Martin Liška
2021-01-06 13:37 ` Martin Liška
2021-01-07 19:03 ` Ian Lance Taylor
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=20201221094837.GG3788@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@golang.org \
--cc=jwakely.gcc@gmail.com \
--cc=mliska@suse.cz \
/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).