From: Michael J Gruber <git@drmicha.warpmail.net>
To: Eli Barzilay <eli@barzilay.org>
Cc: git@vger.kernel.org
Subject: Re: git rev-list formatting
Date: Mon, 22 Mar 2010 14:08:47 +0100 [thread overview]
Message-ID: <4BA76BDF.6060106@drmicha.warpmail.net> (raw)
In-Reply-To: <m3eijcpoud.fsf@winooski.ccs.neu.edu>
Eli Barzilay venit, vidit, dixit 22.03.2010 12:39:
> Eli Barzilay <eli@barzilay.org> writes:
>
>> [...]
>>
>> Also, is there a way to avoid the "commit <sha1>" line, print some
>> information that I specify in the format string, and show the whole
>> message as is (without wrapping or other tweaks)?
>
> Looks like `git log' does something similar to what I want anyway,
> which leads me to a related question -- it's not clear to me what are
> the differences between `git rev-list', `git log', `git diff', and
> `git show', since it looks like they can all be tweaked to produce
> similar outputs. Are they all the same with different outputs? Is
> there some description of them with the differences explained?
The rev-list man page lists all commands of that family, with rev-list
being the bare bones version, and log and friends being more "high
level". log and rev-list walk the revision tree, show does not. Most of
that can be changed through options. whatchanged is a special family
member...
diff is from a completely different family (see git help diff or git
help diffcore). It never walks, but compares revisions (or other things).
The log family never compares things, but can show a patch, i.e. the
difference to the ancestor(s).
> Also related, it looks like `--abbrev-commit' has no effect on `git
> rev-list', but does on `git log', even through it's documented in the
> former's man page. So it looks like either there are more
> (undocumented?) differences, or maybe that's also a bug?
I consider this a bug. In fact, it has an effect, but not a visible one.
You would have to use --abbrev=7 or such.
A patch is upcoming.
Cheers,
Michael
next prev parent reply other threads:[~2010-03-22 13:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-22 11:30 git rev-list formatting Eli Barzilay
2010-03-22 11:39 ` Eli Barzilay
2010-03-22 13:08 ` Michael J Gruber [this message]
2010-03-22 13:36 ` [PATCH] rev-list: heed --abbrev-commit option Michael J Gruber
2010-03-26 19:32 ` Junio C Hamano
2010-03-27 13:30 ` Michael J Gruber
2010-03-22 14:42 ` git rev-list formatting Eli Barzilay
2010-03-22 17:22 ` René Scharfe
2010-03-23 1:57 ` Eli Barzilay
2010-03-23 10:52 ` Michael J Gruber
2010-03-23 11:06 ` Eli Barzilay
2010-03-23 12:26 ` Jeff King
2010-03-23 12:40 ` Erik Faye-Lund
2010-03-23 12:59 ` Eli Barzilay
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=4BA76BDF.6060106@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=eli@barzilay.org \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.