From: "Harvey Harrison" <harvey.harrison@gmail.com>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: git@vger.kernel.org
Subject: Re: tracking renames
Date: Tue, 4 Mar 2008 14:03:54 -0800 [thread overview]
Message-ID: <590657100803041403q2cc68e21p1c92c244939eb148@mail.gmail.com> (raw)
In-Reply-To: <20080304135734.b2c2f473.akpm@linux-foundation.org>
On Tue, Mar 4, 2008 at 1:57 PM, Andrew Morton <akpm@linux-foundation.org> wrote:
>
> When I do
>
> git-whatchanged drivers/watchdog/iTCO_wdt.c
>
git-whatchanged --follow drivers/watchdog/iTCO_wdt.c
Cheers,
Harvey
next prev parent reply other threads:[~2008-03-04 22:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 21:57 tracking renames Andrew Morton
2008-03-04 22:03 ` Harvey Harrison [this message]
2008-03-04 22:10 ` Andrew Morton
2008-03-04 22:19 ` Jakub Narebski
2008-03-05 15:39 ` Jean-François Veillette
2008-03-05 16:15 ` Jakub Narebski
2008-03-07 8:19 ` Steven Grimm
2008-03-05 16:39 ` Johannes Schindelin
2008-03-05 20:54 ` Martin Langhoff
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=590657100803041403q2cc68e21p1c92c244939eb148@mail.gmail.com \
--to=harvey.harrison@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=git@vger.kernel.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 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).