From: Shawn Pearce <spearce@spearce.org>
To: "Brown, Len" <len.brown@intel.com>
Cc: git@vger.kernel.org
Subject: Re: how to display file history?
Date: Mon, 15 May 2006 02:00:54 -0400 [thread overview]
Message-ID: <20060515060054.GA28252@spearce.org> (raw)
In-Reply-To: <CFF307C98FEABE47A452B27C06B85BB670F4F8@hdsmsx411.amr.corp.intel.com>
"Brown, Len" <len.brown@intel.com> wrote:
> it is tiresome to access kernel.org/git tree display
> to see the list of commits that changed a particular file.
> (and for files on my local disk, this isn't available).
>
> How do I print the list of commits that change a particular file
> on my local disk?
I'm confused - why aren't these available on your local disk? Do you
not have a clone of the kernel repository local? If you don't have
a clone you aren't really going to be able to get a history.
But assuming you had one use whatchanged:
git whatchanged A
will show only the commits which affected file A, listing them in
reverse order (most recent to oldest).
--
Shawn.
next prev parent reply other threads:[~2006-05-15 6:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 5:52 how to display file history? Brown, Len
2006-05-15 6:00 ` Shawn Pearce [this message]
2006-05-15 15:15 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2006-05-15 6:13 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
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
2006-05-15 17:24 Brown, Len
2006-05-15 17:54 ` Linus Torvalds
2006-05-15 19:04 Brown, Len
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=20060515060054.GA28252@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--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 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.