git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: how to trace the patch?

From
sean <seanlkml@sympatico.ca>
Date
Apr 27, 2006, 10:57 UTC
Message-ID
<BAYC1-PASMTP029B6CB13A6C0BA3956E17AEBD0@CEZ.ICE>
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

Previous: AubreyNext: Linus Torvalds
Message 2 of 4 in “how to trace the patch?”
  1. AubreyApr 27, 2006
  2. seanApr 27, 2006
  3. Linus TorvaldsApr 27, 2006
  4. AubreyApr 27, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.