From: ebiederm@xmission.com (Eric W. Biederman)
To: Junio C Hamano <junkio@cox.net>
Cc: "Brown, Len" <len.brown@intel.com>, git@vger.kernel.org
Subject: Re: how to display file history?
Date: Mon, 15 May 2006 09:54:36 -0600 [thread overview]
Message-ID: <m1ejyv7077.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <7v64k7wzzf.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Sun, 14 May 2006 23:42:28 -0700")
Junio C Hamano <junkio@cox.net> writes:
> "Brown, Len" <len.brown@intel.com> writes:
>
>>
>>> git whatchanged A
>>
>> thanks. I've used this on entire repos before, but
>> for some reason didn't think of this command name
>> when looking for individual file history.
>
> Probably with recent enough git, one of
>
> git log --stat -- A
> git log -p -- A
> git log -p --full-diff -- A
>
> might be more pleasant, depending on what you are trying to look
> for.
>
> "A" can be a single file, more than one files, a directory,...
So that it has a chance of being remembered, and eventually fixed
the man pages of git-whatchanged and git-log only sort of tell you
that this is even possible. git-whatchanged is certainly worse,
but I don't think if I didn't know to look for it I could see the
fact that these commands take path names from looking at their
man pages.
Eric
next prev parent reply other threads:[~2006-05-15 15:55 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 [this message]
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
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=m1ejyv7077.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=len.brown@intel.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).