From: Linus Torvalds <torvalds@osdl.org>
To: Marco Costalba <mcostalba@gmail.com>
Cc: Junio C Hamano <junkio@cox.net>, Git Mailing List <git@vger.kernel.org>
Subject: Re: gitweb.cgi history not shown
Date: Sun, 11 Jun 2006 09:54:19 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0606110948090.5498@g5.osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0606110933040.5498@g5.osdl.org>
I just like talking to myself.
On Sun, 11 Jun 2006, Linus Torvalds wrote:
>
> git-rev-list --all | git-diff-tree -p -- <filename>
That obviously wants a "--stdin" argument to git-diff-tree, and I might as
well point out that it has a few other differences to doing this with the
"--no-simplify-history" flag:
- git-diff-tree obviously doesn't show merges normally, and when it does,
it would show only merges that change the file. In contrast, the "git
log" approach would show all merges that are part of the resulting
history (which, since you don't simplify merges, is _all_ of them).
- the extra flag to "git log" approach allows "--parents" to work, ie the
stretches of commits in between merges would have their parents
rewritten, so that the history would be a unified whole, and you can
use qgit/gitk to show the result. The above pipeline obviously cannot
do that, since doing the filename limiter in git-diff-tree means that
it doesn't ever even _see_ the "history" part, it's just doing it one
commit at a time.
That concludes my monologue on the matter, I hope. If somebody wants to
condense the issue of "show all history" vs "show how we got to this
state" and add it to the Wiki FAQ thing, that would probably be good.
Linus
next prev parent reply other threads:[~2006-06-11 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-11 5:31 gitweb.cgi history not shown Marco Costalba
2006-06-11 6:02 ` Linus Torvalds
2006-06-11 6:32 ` Marco Costalba
2006-06-11 16:19 ` Linus Torvalds
2006-06-11 16:40 ` Linus Torvalds
2006-06-11 16:54 ` Linus Torvalds [this message]
2006-06-11 16:59 ` Jakub Narebski
2006-06-11 17:57 ` Linus Torvalds
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=Pine.LNX.4.64.0606110948090.5498@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=mcostalba@gmail.com \
/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).