From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to find out which kernel release contains some code
Date: Tue, 14 Sep 2004 15:18:36 -0700 [thread overview]
Message-ID: <20040914151836.5d15e4f0.rddunlap@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0409131132570.3202-100000@ida.rowland.org>
On Mon, 13 Sep 2004 11:41:50 -0400 (EDT) Alan Stern wrote:
| Randy:
|
| Is there any simple easy way to find out in which kernel release a
| particular line of code first appeared? Or to find out whether that line
| is or isn't present in a particular release?
Hi Alan,
I usually try to use BK's web interface "Browse the source tree"
for this:
http://linux.bkbits.net:8080/linux-2.5/src?nav=index.html
E.g., I can browse uhci-hcd.c, version 1.89, and see on what date
and who it thinks was responsible for a line of source code:
http://linux.bkbits.net:8080/linux-2.5/anno/drivers/usb/host/uhci-hcd.c%401.89?nav=index.html|src/.|src/drivers|src/drivers/usb|src/drivers/usb/host
But that won't say what kernel version it is (first) contained in.
Just a merge date.
| The timestamps in BitKeeper don't help much. They seem to reflect the
| first time the code was put into _any_ BitKeeper repository, not the time
| it was entered into Linus's tree.
Yes, that bugs me too.
| The web interface to the linux-2.6 tree
| doesn't offer any way to view a particular source file as of a particular
| release tag.
|
| I don't fancy downloading lots and lots of enormous patch files, searching
| for one small entry. Or lots of kernel source tarballs, for that matter.
|
| There's got to be an easier way. Do you know of one?
Not really. You could ask on the bk-users mailing list. See here:
http://www.bitkeeper.com/Support.Mailing.html
Or there may be features in the commercial version of BK that help
out with this more that the free version does. I dunno.
--
~Randy
prev parent reply other threads:[~2004-09-14 22:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 15:41 Alan Stern
2004-09-14 22:18 ` Randy.Dunlap [this message]
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=20040914151836.5d15e4f0.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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
all inboxes | Powered by JetHome®