From: Jonathan Nieder <jrnieder@gmail.com>
To: Daniel F <nanotube@gmail.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Tor Arntsen" <tor@spacetec.no>,
"Jay Soffian" <jaysoffian@gmail.com>,
git@vger.kernel.org
Subject: Re: git am mangles commit author name.
Date: Fri, 16 Jul 2010 14:19:54 -0500 [thread overview]
Message-ID: <20100716191954.GB16371@burratino> (raw)
In-Reply-To: <AANLkTimIkepwy93dYCu5mkdSMHNuh3dbMyxcHPl4hGmt@mail.gmail.com>
Hi Daniel,
Daniel F wrote:
> would simply setting minimum length to 1 have any negative
> side effects?
I am not a git maintainer, but I would suggest writing a patch to do
that. Then you can try it and see, and send us a copy of the patch
when reporting the results.
My guess is Linus wanted to make sure he had meaningful names in
patches he applies[1]. There is no technical limit I know of that would
lead one to forbid an author name longer than 60 characters, either.
So the questions are:
- did any code learn to rely on those limits later?
- are any _people_ relying on those limits now?
I suspect the answer to question 2, at least for the lower bound,
is no.
Hope that helps,
Jonathan
[1] See v0.99.2~51^2~21 (Start of early patch applicator tools for
git., 2005-04-11) for the original script.
prev parent reply other threads:[~2010-07-16 19:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 3:53 git am mangles commit author name Daniel F
2010-07-13 5:49 ` Jonathan Nieder
2010-07-13 14:54 ` Daniel F
2010-07-13 15:11 ` Jay Soffian
2010-07-13 15:48 ` Daniel F
2010-07-13 22:16 ` Ævar Arnfjörð Bjarmason
2010-07-14 14:16 ` Tor Arntsen
2010-07-14 14:31 ` Ævar Arnfjörð Bjarmason
2010-07-16 14:18 ` Daniel F
2010-07-16 19:19 ` Jonathan Nieder [this message]
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=20100716191954.GB16371@burratino \
--to=jrnieder@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=jaysoffian@gmail.com \
--cc=nanotube@gmail.com \
--cc=tor@spacetec.no \
/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