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

Re: determine a linux kernel version of a patch file

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
May 14, 2015, 17:25 UTC
Message-ID
<041beaedd8018f1759158e488b29a42b@www.dscho.org>
In-Reply-To
<CAJmOuExq3WF26Gufr5bAA7w3=EMxJ80NKMXf8Dgi0TK7kVXStA@mail.gmail.com>
Hi Pawel,
On 2015-05-14 19:08, Pawel Por wrote:
Show 11 quoted lines
> Most patches contain the index line. Is it the well known git index
> (staging area) ?
> Can I use the index to find the exact kernel version from which a
> patch was created.
> Please look at an example patch sent to LKML:
> https://lkml.org/lkml/2015/5/14/497
> 
> It contains the following index line:
> index 8dd1e55..9b0c81e 100644
> 
> I tried to find it using "git log" but I couldn't.
If you call `git log --raw` (possibly adding --all) and then search for 8dd1e55, you should at least get to the revision when this file was changed to the revision that served as base for the patch. To make it faster, you could call `git log --raw -- <filename>`. That would also have the advantage that you could scroll up again to see which revision, if any, modified the file again, giving you kind of a commit range from which to pick.

Ciao, Johannes

Previous: Pawel PorNext: Matthieu Moy
Message 2 of 6 in “determine a linux kernel version of a patch file”
  1. Pawel PorMay 14, 2015
  2. Johannes SchindelinMay 14, 2015
  3. Matthieu MoyMay 15, 2015
  4. Kelvin LiMay 15, 2015
  5. Johannes SchindelinMay 15, 2015
  6. Junio C HamanoMay 15, 2015

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.