From: Frank Cusack <fcusack@fcusack.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: bkbits source browsing -- tags
Date: Thu, 4 Sep 2003 06:51:15 -0700 [thread overview]
Message-ID: <20030904065115.B12018@google.com> (raw)
I really like the source browser on linux.bkbits.net.
Is there a way to browse to a file and see which rev is in which kernel
version? The closest thing I can find is that if I follow the 'CSet'
link, sometimes the Rev data is yellow and has what I'm guessing is a
tag. But this is clearly not comprehensive.
eg, arch/i386/kernel/apic.c doesn't come close to telling me which is
the apic.c found in (say) 2.4.21.
If there's a way to do this directly from the source browser, that'd
be perfect, but also if there's a way to correlate it somehow with
data I can get elsewhere that's fine too. eg, from the "start page"
at linux.bkbits.net, if I go to 'Tags', I can find the 2.4.21 tag
("MailDone v2.4.21" I guess is it) and click 'later CSets' but that
information doesn't seem particularly helpful in finding 2.4.21 apic.c.
(Obviously, I'm not even really sure how to read that data.)
thanks
/fc
reply other threads:[~2003-09-04 13:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030904065115.B12018@google.com \
--to=fcusack@fcusack.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