From: Clemens Ladisch <clemens@ladisch.de>
To: James Courtier-Dutton <james.dutton@gmail.com>
Cc: LKML Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Comparing linux kernel trees.
Date: Sun, 20 Jan 2013 14:27:51 +0100 [thread overview]
Message-ID: <50FBF0D7.703@ladisch.de> (raw)
In-Reply-To: <CAAMvbhGM+s0LKJVqR8GWz4LkBhSZCCT_xa2qh=dFjV8A92jqOg@mail.gmail.com>
James Courtier-Dutton wrote:
> I have been given a linux kernel sources tar file.
> It contains a modified version of the linux kernel.
> It is just source files, without any "git" history.
> What I would like to do is compare this with the mainline linux kernel
> git tree, and find the tag from the kernel git tree that this source
> code is most similar to.
The kernel *knows* which version it is.
> My plan at the moment is just to automate a checkout of every git tag,
> then run diff -ur on it, and then choose the smallest diff file
> output.
> But, has anyone got a better method?
head -5 Makefile
Regards,
Clemens
next prev parent reply other threads:[~2013-01-20 13:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 11:20 Comparing linux kernel trees James Courtier-Dutton
2013-01-20 13:27 ` Clemens Ladisch [this message]
2013-01-20 16:06 ` James Courtier-Dutton
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=50FBF0D7.703@ladisch.de \
--to=clemens@ladisch.de \
--cc=james.dutton@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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