From: Junio C Hamano <gitster@pobox.com>
To: "Thomas J. Faughnan Jr." <thomas@faughnan.net>
Cc: Jeff King <peff@peff.net>,
"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, 31 Jul 2023 08:56:09 -0700 [thread overview]
Message-ID: <xmqq351413dy.fsf@gitster.g> (raw)
In-Reply-To: <CUFTY8BW9NHM.132KSE56BDE8Q@badwolf> (Thomas J. Faughnan, Jr.'s message of "Sun, 30 Jul 2023 17:38:13 -0400")
"Thomas J. Faughnan Jr." <thomas@faughnan.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.
>
> Would this change still be considered? Or alternatively a git config
> option to ignore "." when checking if a character is crud?
That is certainly a blast from the past ;-)
I actually was wondering the opposite should be done, i.e. be
consistent and remove '.' just like '<' and '>' even from the
middle of names. '.' in the human-readable name part anywhere on
To: and Cc: lines, not just at the end, causes mailers to barf,
unless such name is quoted.
And from the consistency point of view, I think that a configuration
variable that tells Git to include/exclude "." from the "crud()"
letter should make us drop/keep "." from anywhere in the name, not
just at the tail end. If we decide that adding such a configuration
variable is a good idea, that is.
next prev parent reply other threads:[~2023-07-31 15:56 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
2023-07-30 21:38 ` Thomas J. Faughnan Jr.
2023-07-31 15:56 ` Junio C Hamano [this message]
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=xmqq351413dy.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=danpltile@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
--cc=thomas@faughnan.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.