From: Jonas Fonseca <fonseca@diku.dk>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
Junio C Hamano <junkio@cox.net>,
"Brown, Len" <len.brown@intel.com>,
git@vger.kernel.org
Subject: Re: how to display file history?
Date: Sun, 21 May 2006 19:35:49 +0200 [thread overview]
Message-ID: <20060521173549.GA23347@diku.dk> (raw)
In-Reply-To: <m164k76ylb.fsf@ebiederm.dsl.xmission.com>
Eric W. Biederman <ebiederm@xmission.com> wrote Mon, May 15, 2006:
> Linus Torvalds <torvalds@osdl.org> writes:
>
> > On Mon, 15 May 2006, Eric W. Biederman wrote:
> > People still don't seem to realize how flexible (and powerful) the git
> > revision specifications are. It's not just limiting by path, all of these
> > work on _all_ of the "history tools" (whether they be gitk, qgit, "git
> > log", "git whatchanged" or your own home-cooked stuff):
> >
> > [examples]
>
> But regardless of where we put it, it needs to be documented someplace
> besides in the email so you don't need to read the code to see that
> the option is there.
I've put some of this on http://git.or.cz/gitwiki/RevisionSpecification
that for now may serve as an introduction ...
--
Jonas Fonseca
next prev parent reply other threads:[~2006-05-21 17:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 6:13 how to display file history? Brown, Len
2006-05-15 6:42 ` Junio C Hamano
2006-05-15 15:54 ` Eric W. Biederman
2006-05-15 16:15 ` Linus Torvalds
2006-05-15 16:29 ` Eric W. Biederman
2006-05-15 16:45 ` Linus Torvalds
2006-05-15 17:55 ` J. Bruce Fields
2006-05-21 17:35 ` Jonas Fonseca [this message]
2006-05-15 17:22 ` Marco Costalba
2006-05-15 18:03 ` Linus Torvalds
2006-05-15 18:32 ` Marco Costalba
2006-05-15 18:51 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2006-05-15 19:04 Brown, Len
2006-05-15 17:24 Brown, Len
2006-05-15 17:54 ` Linus Torvalds
2006-05-15 5:52 Brown, Len
2006-05-15 6:00 ` Shawn Pearce
2006-05-15 15:15 ` 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=20060521173549.GA23347@diku.dk \
--to=fonseca@diku.dk \
--cc=ebiederm@xmission.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=len.brown@intel.com \
--cc=torvalds@osdl.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.