From: Eric Wong <normalperson@yhbt.net>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] rev-list: honor --abbrev=<n> when doing --pretty=oneline
Date: Thu, 6 Apr 2006 20:13:56 -0700 [thread overview]
Message-ID: <20060407031356.GA25525@hand.yhbt.net> (raw)
In-Reply-To: <7v64lmuqa5.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
> Eric Wong <normalperson@yhbt.net> writes:
>
> > Note that --abbrev=DEFAULT_ABBREV was on by default before, but
> > it only affected the printing of the Merge: header). Let me
> > know if anybody doesn't want the default behavior to change.
>
> I've never felt need for abbreviating commit object names, so I
> only had the abbrev variable to determine how the merge parents
> are shown. If you want to abbreviate the commit object names as
> well, you _could_ do independent precision for parents and
> commits, but that would be overkil. So I'd rather see a switch
> to turn abbreviation for commits on, perhaps like this:
>
> $ git-rev-list --pretty=oneline --abbrev-commit -n 3 master
> 454a35b Add documentation for git-imap-send.
> ba3c937 blame.c: fix completely broken ancestry traversal.
> 6cbd5d7 Tweaks to make asciidoc play nice.
>
> $ git-rev-list --pretty=oneline --abbrev=4 --abbrev-commit -n 3 master
> 454a Add documentation for git-imap-send.
> ba3c9 blame.c: fix completely broken ancestry traversal.
> 6cbd5 Tweaks to make asciidoc play nice.
>
> Otherwise you might break Porcelains and people's scripts that
> read from --pretty or --header output.
>
> -- >8 --
Sounds good, I like your patch. I'm not thrilled with the length of the
'--abbrev-commit' switch, but I guess that's what aliases are for :>
--
Eric Wong
prev parent reply other threads:[~2006-04-07 3:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 0:44 [PATCH] rev-list: honor --abbrev=<n> when doing --pretty=oneline Eric Wong
2006-04-07 1:29 ` Junio C Hamano
2006-04-07 3:13 ` Eric Wong [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=20060407031356.GA25525@hand.yhbt.net \
--to=normalperson@yhbt.net \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).