From: Jeff King <peff@peff.net>
To: "Robin H. Johnson" <robbat2@gentoo.org>
Cc: Kacper Kornet <draenog@pld-linux.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Apostrophe at the end of author name
Date: Fri, 29 Jun 2012 13:43:58 -0400 [thread overview]
Message-ID: <20120629174358.GB3804@sigill.intra.peff.net> (raw)
In-Reply-To: <robbat2-20120629T170457-788694600Z@orbis-terrarum.net>
On Fri, Jun 29, 2012 at 05:05:31PM +0000, Robin H. Johnson wrote:
> On Fri, Jun 29, 2012 at 02:41:22PM +0200, Kacper Kornet wrote:
> > I try to import some repositories into git and one of the developers has
> > asked his name to be presented as: Name 'Nick' <email>.
> > However git commit --author="Name 'Nick' <email>" strips the last
> > apostrophe and produces a commit authored by: Name 'Nick <email>.
> >
> > Maybe the function strbuf_addstr_without_crud in ident.c should strip
> > the trailing apostrophe only when it removed it also from the beginning
> > of the string?
> Which version of Git? And is it being stripped by git, or one of the
> import tools?
I'm sure it's the most recent one, as strbuf_addstr_without_crud was
only added recently (but it is a refactoring of older code which should
have the same behavior). We had a similar complaint recently that
"A.B.C. <abc@example.com>" has its trailing dot stripped, even though
the internal ones are retained.
Those stripping rules date back to very early versions of git to try to
clean up cruft from gecos or other unreliable sources. I wonder if we
are better off being a bit more liberal.
-Peff
next prev parent reply other threads:[~2012-06-29 17:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 12:41 Apostrophe at the end of author name Kacper Kornet
2012-06-29 17:05 ` Robin H. Johnson
2012-06-29 17:43 ` Jeff King [this message]
2012-06-29 18:17 ` Kacper Kornet
2012-06-29 18:29 ` Jeff King
2012-06-29 19:04 ` Junio C Hamano
2012-06-29 19:35 ` Jeff King
2012-06-29 19:59 ` Kacper Kornet
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=20120629174358.GB3804@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=draenog@pld-linux.org \
--cc=git@vger.kernel.org \
--cc=robbat2@gentoo.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).