From: Danh Doan <congdanhqx@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git v2.25.0-rc0
Date: Sat, 28 Dec 2019 19:54:33 +0700 [thread overview]
Message-ID: <20191228125433.GC24268@danh.dev> (raw)
In-Reply-To: <xmqq36d5jtck.fsf@gitster-ct.c.googlers.com>
On 2019-12-27 14:28:59-0800, Junio C Hamano <gitster@pobox.com> wrote:
> Danh Doan <congdanhqx@gmail.com> writes:
> > 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?
Back in the days, I had my IME started on logging in,
then to save some tiny time on starting up,
I turned it off.
>
> 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).
Yes, that's the the right way to do, but I didn't pick that way.
I'm going through my ~/src and fixing it.
Thanks,
--
Danh
next prev parent reply other threads:[~2019-12-28 12:54 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
2019-12-28 12:54 ` Danh Doan [this message]
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=20191228125433.GC24268@danh.dev \
--to=congdanhqx@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 NNTP newsgroup(s).