From: "Jon Smirl" <jonsmirl@gmail.com>
To: "linux@horizon.com" <linux@horizon.com>
Cc: git@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: Digging through old vendor code
Date: Sun, 13 Jan 2008 12:04:17 -0500 [thread overview]
Message-ID: <9e4733910801130904n7f311915tba4aa5b766c7a9bc@mail.gmail.com> (raw)
In-Reply-To: <20080113162806.13991.qmail@science.horizon.com>
The vendor gave me an edited file with support for their device. The
original was copied from the kernel somewhere around 2.6.15 and then
edited. Nobody remembers what the source file was but there are a
couple of fairly close matches.
Diffing against the current kernel mixes the two sets of changes -
what the vendor did and what changed in the core kernel. I'm sorting
this out by hand but it is 3,000 lines of diffs.
It is an interesting problem to use the git history to try and
discover the original source file.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2008-01-13 17:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-13 16:28 Digging through old vendor code linux
2008-01-13 17:04 ` Jon Smirl [this message]
2008-01-13 17:31 ` Jon Smirl
2008-01-14 12:08 ` Jeff King
2008-01-14 14:49 ` Jon Smirl
-- strict thread matches above, loose matches on Subject: below --
2008-01-13 4:09 Jon Smirl
2008-01-13 4:41 ` Linus Torvalds
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=9e4733910801130904n7f311915tba4aa5b766c7a9bc@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=git@vger.kernel.org \
--cc=linux@horizon.com \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).