From: Junio C Hamano <gitster@pobox.com>
To: Danh Doan <congdanhqx@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git v2.25.0-rc0
Date: Fri, 27 Dec 2019 14:28:59 -0800 [thread overview]
Message-ID: <xmqq36d5jtck.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <20191227113858.GB24268@danh.dev> (Danh Doan's message of "Fri, 27 Dec 2019 18:38:58 +0700")
Danh Doan <congdanhqx@gmail.com> writes:
> On 2019-12-26 09:50:49-0800, Junio C Hamano <gitster@pobox.com> wrote:
>> Danh Doan <congdanhqx@gmail.com> writes:
>>
>> > My name should be moved down to next paragraph,
>> > since I was lazy to type my name with all accents.
>>
>> Your first contribution was back in v2.20 days, and then the recent
>> ones are all within this cycle for v2.25.
>>
>> I am a bit curious why you need to avoid being lazy just to give the
>> correct name to your commits, though. Isn't
>
> Some of my projects requires ASCII-only user.name,
> instead of doing the right thing
>
> git config user.name <simplified-name>
>
> I decided to set it globally instead.
> I rarely need to type in my native language,
> hence I don't have the IME software start with Xorg.
Hmph, but back in v2.20 days, you did have IME?
In any case, if I were in such a situation to need my name spelled
differently depending on the project I work on, I would probably use
$ git config --global user.name <simplified-name>
$ cd <repository of git>
$ git config user.name <name-with-accents>
or the other way around (depends on which projects your focus is on).
But perhaps that is not so useful to your situation?
next prev parent reply other threads:[~2019-12-27 22:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-25 21:44 [ANNOUNCE] Git v2.25.0-rc0 Junio C Hamano
2019-12-26 0:33 ` Denton Liu
2019-12-26 14:35 ` Danh Doan
2019-12-26 17:50 ` Junio C Hamano
2019-12-27 11:38 ` Danh Doan
2019-12-27 22:28 ` Junio C Hamano [this message]
2019-12-28 12:54 ` Danh Doan
2019-12-29 19:39 ` Git for Windows v2.25.0-rc0, was " Johannes Schindelin
2020-01-02 22:19 ` Taylor Blau
2020-01-03 19:39 ` Johannes Schindelin
2020-01-04 17:58 ` Taylor Blau
2020-01-04 23:13 ` Junio C Hamano
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=xmqq36d5jtck.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=congdanhqx@gmail.com \
--cc=git@vger.kernel.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 NNTP newsgroup(s).