From: sean <seanlkml@sympatico.ca>
To: Aubrey <aubreylee@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: how to trace the patch?
Date: Thu, 27 Apr 2006 06:57:28 -0400 [thread overview]
Message-ID: <BAYC1-PASMTP029B6CB13A6C0BA3956E17AEBD0@CEZ.ICE> (raw)
Message-ID: <20060427065728.35a4ae51.seanlkml@sympatico.ca> (raw)
In-Reply-To: <6d6a94c50604270306j44c280bdo283591f2f595f74e@mail.gmail.com>
On Thu, 27 Apr 2006 18:06:09 +0800
Aubrey <aubreylee@gmail.com> wrote:
> When I update the kernel git tree a few days later, you know, there
> could be a lot of patches. Then I found one file changed, how can I
> know which patch the modification belong to?
> How can I find the patch?
Hi Aubrey,
$ git log -- <filename>
To see a list of commits that affected the file you're interested in.
$ git log -p -- <filename>
Will include a diff after each commit showing you how the file was
changed. And if you want to see what other changes happened in each
commit that modified your file, add "--full-diff" to the command above.
Note that you can also replace the <filename> with a <directory>
to see a list of commits that affected any file below that directory.
HTH,
Sean
next prev parent reply other threads:[~2006-04-27 11:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 10:06 how to trace the patch? Aubrey
[not found] ` <20060427065728.35a4ae51.seanlkml@sympatico.ca>
2006-04-27 10:57 ` sean [this message]
2006-04-27 15:55 ` Linus Torvalds
2006-04-27 16:19 ` Aubrey
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=BAYC1-PASMTP029B6CB13A6C0BA3956E17AEBD0@CEZ.ICE \
--to=seanlkml@sympatico.ca \
--cc=aubreylee@gmail.com \
--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).