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 15, 2015, 17:41 UTC
Message-ID
<c97f7591e4bf884ee810699f1e5278dd@www.dscho.org>
In-Reply-To
<1431709433.1401.9.camel@gmail.com>
Hi,
On 2015-05-15 19:03, Kelvin Li wrote:
Show 25 quoted lines
> On Fri, 2015-05-15 at 14:08 +0200, Matthieu Moy wrote:
>> Pawel Por <porparek@gmail.com> writes:
>>
>> > At the beginning I'm sorry if this post is completely unrelated to
>> > this mailing list.
>> > I'm trying to find the base linux kernel version from which a patch
>> > has been created and posted to LKML.
>> > Most patches contain the index line. Is it the well known git index
>> > (staging area) ?
>>
>> This is the id of the blob object corresponding to the _file_ being
>> patched (index <from>..<to> <mode>). That's why you don't see it in git
>> log: git log shows you ids for commit objects (which point to trees,
>> which in turn points to blob).
>>
>> See Johannes' answer for how you can get some possible commits.
>>
> 
> Come to think of it, why is that line named "index"? Conceptually, this
> "diff header index" seems distinct from the "staging area index", but
> calling both "index" is confusing, in my opinion.
> 
> Is there already a note about this in the docs somewhere? At the very
> least, "git help diff" seems to happily use both senses of the word
> without any acknowledgement that we're overloading it.
By default, `git diff` works on the index, unless you force it to compare revisions or the working directory to a revision. I guess that is where the wording comes from.
In any case, it is too late to change it now...

Ciao, Johannes

Previous: Kelvin LiNext: Junio C Hamano
Message 5 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.