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:22:37 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0805301320460.3141@woody.linux-foundation.org> (raw)
In-Reply-To: <20080530194635.GI593@machine.or.cz>
On Fri, 30 May 2008, Petr Baudis wrote:
>
> Because it confused me, I'm probably not the first to be confused and it
> will probably confuse others in the future too. The UI should be more
> consistent.
Btw, the reason this is irrelevant is that "git rev-list" isn't even a UI.
It's internal plumbing, and almost all of it's flags etc are directly from
historical reasons. IOW, it does bisection because it used to be the only
program that did any revision walking. It can do pretty much what git log
does for the same reason.
So breaking git rev-list because somebody thinks it's "UI" is odd totally
misses the whole _point_ of the command.
Linus
next prev parent reply other threads:[~2008-05-30 20:23 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
2008-05-30 21:34 ` Petr Baudis
2008-05-30 20:22 ` Linus Torvalds [this message]
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.0805301320460.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).