From: Linus Torvalds <torvalds@linux-foundation.org>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: git-log vs git-rev-list
Date: Fri, 30 May 2008 13:20:13 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0805301316580.3141@woody.linux-foundation.org> (raw)
In-Reply-To: <20080530194635.GI593@machine.or.cz>
On Fri, 30 May 2008, Petr Baudis wrote:
> >
> > Why would you want to use "git-rev-list" at all?
>
> Because it was the natural command to access history from a script to me
> and nothing in the documentation hinted me that I shouldn't use it.
So use it. Or not.
Just don't think it's the same as "git log".
> Step back a bit: it's git-_REV_-list. Technically, --all --objects is
> nonsensical operation to do on revision list either.
Who cares?
Why are you arguing against *facts*?
The *fact* is, git rev-list can traverse the whole object chain.
The *fact* is that git rev-list can do other operations that have nothing
to do with logs (bisection, for example).
The *fact* is that both git rev-list and git log can traverse a set of
revisions, but that doesn't make them the same command.
I totally don't see your arguments. They are pointless. git rev-list and
git log already share all the relevant internal machinery for the things
where they overlap in capabilities. And the fact that they output
different things is because they are different.
Linus
next prev parent reply other threads:[~2008-05-30 20:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 16:56 git-log vs git-rev-list Petr Baudis
2008-05-30 17:25 ` Linus Torvalds
2008-05-30 19:46 ` Petr Baudis
2008-05-30 20:20 ` Linus Torvalds [this message]
2008-05-30 21:34 ` Petr Baudis
2008-05-30 20:22 ` Linus Torvalds
2008-05-30 20:28 ` Junio C Hamano
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=alpine.LFD.1.10.0805301316580.3141@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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).