threads / discuss / 39336

determine a linux kernel version of a patch file

Subject: determine a linux kernel version of a patch file

## tl;dr

6 messages between May 14, 2015 and May 15, 2015.

replies: 5people: 5as markdown or json

Pawel Por· May 14, 2015, 17:08 UTC · lore

Hi,

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) ? 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.

Please help me to determine the exact kernel version.

thanks in advance

Johannes Schindelin· May 14, 2015, 17:25 UTC · re: Pawel Por · lore

Re: determine a linux kernel version of a patch file

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

Matthieu Moy· May 15, 2015, 12:08 UTC · re: Pawel Por · lore

Re: determine a linux kernel version of a patch file

Pawel Por <porparek@gmail.com> writes:

Show 8 quoted lines

> Hi,
>
> 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.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

Kelvin Li· May 15, 2015, 17:03 UTC · re: Matthieu Moy · lore

Re: determine a linux kernel version of a patch file

On Fri, 2015-05-15 at 14:08 +0200, Matthieu Moy wrote:

Show 18 quoted lines

> Pawel Por <porparek@gmail.com> writes:
> 
> > Hi,
> >
> > 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.

Thanks, Kelvin

Johannes Schindelin· May 15, 2015, 17:41 UTC · re: Kelvin Li · lore

Re: determine a linux kernel version of a patch file

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

Junio C Hamano· May 15, 2015, 20:16 UTC · re: Johannes Schindelin · lore

Re: determine a linux kernel version of a patch file

Johannes Schindelin <johannes.schindelin@gmx.de> writes:

Show 5 quoted lines

> 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...

Those who are interested in the full answer can look at this thread.

  http://thread.gmane.org/gmane.comp.version-control.git/9694/focus=9795

;-)