From: Linus Torvalds <torvalds@osdl.org>
To: Luben Tuikov <ltuikov@yahoo.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: Enable tree (directory) history display
Date: Mon, 27 Feb 2006 11:56:07 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0602271154400.22647@g5.osdl.org> (raw)
In-Reply-To: <20060227185554.75822.qmail@web31810.mail.mud.yahoo.com>
On Mon, 27 Feb 2006, Luben Tuikov wrote:
>
> This patch allows history display of whole trees/directories,
> a la "git-rev-list HEAD <dir or file>", but somewhat
> slower, since exported git repository doesn't have
> the files checked out so we have to use
> "$gitbin/git-rev-list $hash | $gitbin/git-diff-tree -r --stdin \'$file_name\'"
No no.
Just use
git-rev-list $hash -- $file_name
where the "--" is the important part.
As a usability-enhancer, you can leave out the "--" to separate filenames
and other things, but when you leave out the "--", git requires that the
filenames exist.
Linus
prev parent reply other threads:[~2006-02-27 19:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 18:55 [PATCH] gitweb: Enable tree (directory) history display Luben Tuikov
2006-02-27 19:56 ` Linus Torvalds [this message]
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.0602271154400.22647@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=ltuikov@yahoo.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).