From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: Pawel Por <porparek@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: determine a linux kernel version of a patch file
Date: Thu, 14 May 2015 19:25:05 +0200 [thread overview]
Message-ID: <041beaedd8018f1759158e488b29a42b@www.dscho.org> (raw)
In-Reply-To: <CAJmOuExq3WF26Gufr5bAA7w3=EMxJ80NKMXf8Dgi0TK7kVXStA@mail.gmail.com>
Hi Pawel,
On 2015-05-14 19:08, Pawel Por wrote:
> 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
next prev parent reply other threads:[~2015-05-14 17:25 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 [this message]
2015-05-15 12:08 ` Matthieu Moy
2015-05-15 17:03 ` Kelvin Li
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=041beaedd8018f1759158e488b29a42b@www.dscho.org \
--to=johannes.schindelin@gmx.de \
--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).