From: Kelvin Li <ltwisabc@gmail.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Pawel Por <porparek@gmail.com>, git@vger.kernel.org
Subject: Re: determine a linux kernel version of a patch file
Date: Fri, 15 May 2015 10:03:53 -0700 [thread overview]
Message-ID: <1431709433.1401.9.camel@gmail.com> (raw)
In-Reply-To: <vpqr3qicabd.fsf@anie.imag.fr>
On Fri, 2015-05-15 at 14:08 +0200, Matthieu Moy wrote:
> 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
next prev parent reply other threads:[~2015-05-15 17:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 17:08 determine a linux kernel version of a patch file Pawel Por
2015-05-14 17:25 ` Johannes Schindelin
2015-05-15 12:08 ` Matthieu Moy
2015-05-15 17:03 ` Kelvin Li [this message]
2015-05-15 17:41 ` Johannes Schindelin
2015-05-15 20:16 ` Junio C Hamano
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=1431709433.1401.9.camel@gmail.com \
--to=ltwisabc@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=porparek@gmail.com \
/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).