From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
"Daniel P." <danpltile@gmail.com>,
git@vger.kernel.org
Subject: Re: Git is removing . from the last part of user.name
Date: Mon, 23 Aug 2021 09:25:10 -0700 [thread overview]
Message-ID: <xmqqsfz0qgbd.fsf@gitster.g> (raw)
In-Reply-To: <YSKleNynVrWWyyML@coredump.intra.peff.net> (Jeff King's message of "Sun, 22 Aug 2021 15:28:56 -0400")
Jeff King <peff@peff.net> writes:
> On a somewhat lesser note, I'm tempted to say that "." probably was
> never that useful (compared to say, comma, which is the gecos
> separator), and we could probably just drop it from the crud list.
Yeah, the only excuse I can think of using to justify treating "."
any specially can be seen in the contrast between the To: and Cc:
header of this message, where the human-readable part of brian and
daniel must be inside a pair of double-quotes while your name needs
no such quoting.
But we do not remove "crud()" crud from the middle, so that's not
even it (the only crud we remvoe from the middle are newlines and
'<' and '>').
next prev parent reply other threads:[~2021-08-23 16:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-22 14:19 Git is removing . from the last part of user.name Daniel P.
2021-08-22 15:33 ` brian m. carlson
2021-08-22 19:28 ` Jeff King
2021-08-22 19:35 ` Jeff King
2021-08-23 16:25 ` Junio C Hamano [this message]
2023-07-30 21:38 ` Thomas J. Faughnan Jr.
2023-07-31 15:56 ` Junio C Hamano
2023-07-31 21:02 ` brian m. carlson
2023-07-31 21:44 ` [PATCH] ident: don't consider trailing dot crud brian m. carlson
2023-07-31 21:49 ` Junio C Hamano
2023-08-02 16:49 ` Junio C Hamano
2023-08-02 21:27 ` brian m. carlson
2023-08-02 21:38 ` Junio C Hamano
2023-07-31 21:56 ` Thomas J. Faughnan Jr.
2023-07-31 22:05 ` 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=xmqqsfz0qgbd.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=danpltile@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
/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).