From: Junio C Hamano <junkio@cox.net>
To: Eric Wong <normalperson@yhbt.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] rev-list: honor --abbrev=<n> when doing --pretty=oneline
Date: Thu, 06 Apr 2006 18:29:22 -0700 [thread overview]
Message-ID: <7v64lmuqa5.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060407004455.GF15743@hand.yhbt.net> (Eric Wong's message of "Thu, 6 Apr 2006 17:44:55 -0700")
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 --
diff --git a/rev-list.c b/rev-list.c
index 22141e2..1301502 100644
--- a/rev-list.c
+++ b/rev-list.c
@@ -30,6 +30,7 @@ static const char rev_list_usage[] =
" --unpacked\n"
" --header | --pretty\n"
" --abbrev=nr | --no-abbrev\n"
+" --abbrev-commit\n"
" special purpose:\n"
" --bisect"
;
@@ -39,6 +40,7 @@ struct rev_info revs;
static int bisect_list = 0;
static int verbose_header = 0;
static int abbrev = DEFAULT_ABBREV;
+static int abbrev_commit = 0;
static int show_timestamp = 0;
static int hdr_termination = 0;
static const char *commit_prefix = "";
@@ -52,7 +54,10 @@ static void show_commit(struct commit *c
fputs(commit_prefix, stdout);
if (commit->object.flags & BOUNDARY)
putchar('-');
- fputs(sha1_to_hex(commit->object.sha1), stdout);
+ if (abbrev_commit && abbrev)
+ fputs(find_unique_abbrev(commit->object.sha1, abbrev), stdout);
+ else
+ fputs(sha1_to_hex(commit->object.sha1), stdout);
if (revs.parents) {
struct commit_list *parents = commit->parents;
while (parents) {
@@ -317,6 +322,14 @@ int main(int argc, const char **argv)
}
if (!strcmp(arg, "--no-abbrev")) {
abbrev = 0;
+ continue;
+ }
+ if (!strcmp(arg, "--abbrev")) {
+ abbrev = DEFAULT_ABBREV;
+ continue;
+ }
+ if (!strcmp(arg, "--abbrev-commit")) {
+ abbrev_commit = 1;
continue;
}
if (!strncmp(arg, "--abbrev=", 9)) {
next prev parent reply other threads:[~2006-04-07 1:29 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 [this message]
2006-04-07 3:13 ` Eric Wong
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=7v64lmuqa5.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.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).