From: "Ted Ts'o" <tytso@mit.edu>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
git@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Minimum git commit abbrev length (Was Re: -tip: origin tree build failure (was: [GIT PULL] ext4 update) for 2.6.37)
Date: Thu, 28 Oct 2010 13:27:25 -0400 [thread overview]
Message-ID: <20101028172725.GA6814@thunk.org> (raw)
In-Reply-To: <20101028171701.GA18368@elte.hu>
On Thu, Oct 28, 2010 at 07:17:01PM +0200, Ingo Molnar wrote:
> > Linus Torvalds <torvalds@linux-foundation.org> wrote:
> > Yes. Except for the kernel the default git commit abbreviation is
> > borderline too short. Seven hex-chars can easily alias with a few
> > more pulls from me: git will not give aliases at the time it gives
> > a shorthand, but a month or two later the abbreviated commit may
> > no longer be unique.
> >
> > So I suggest using --abbrev=12 or similar.
>
> ok. A helper script i use does this:
>
> git log --pretty=format:"%h: %s" $@
>
> I have added --abbrev=12. Might make sense to lengthen the %h
> default in upstream Git as well?
Maybe the right thing to do is add a git config option which allows
for a configurable minimum git commit abbreviation length?
- Ted
next prev parent reply other threads:[~2010-10-28 17:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 4:52 [GIT PULL] ext4 update for 2.6.37 Theodore Ts'o
2010-10-28 7:50 ` Markus Trippelsdorf
2010-10-28 7:56 ` -tip: origin tree build failure (was: [GIT PULL] ext4 update for 2.6.37) Ingo Molnar
2010-10-28 12:12 ` Theodore Tso
2010-10-28 16:30 ` Linus Torvalds
2010-10-28 16:38 ` Ingo Molnar
2010-10-28 16:55 ` Ted Ts'o
2010-10-28 17:00 ` Linus Torvalds
2010-10-28 17:17 ` Ingo Molnar
2010-10-28 17:27 ` Ted Ts'o [this message]
2010-10-28 18:28 ` Minimum git commit abbrev length (Was Re: -tip: origin tree build failure (was: [GIT PULL] ext4 update) " Linus Torvalds
2010-10-28 18:54 ` Linus Torvalds
2010-10-28 21:39 ` -tip: origin tree build failure Junio C Hamano
2010-10-28 21:50 ` Linus Torvalds
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=20101028172725.GA6814@thunk.org \
--to=tytso@mit.edu \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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