All of lore.kernel.org
 help / color / mirror / Atom feed
From: patrick mcmanus <mcmanus@ducksong.com>
To: linux-kernel@vger.kernel.org
Subject: Re: linux.bkbits.net question: mapping cset to kernel version?
Date: Wed, 18 May 2005 12:36:04 -0400	[thread overview]
Message-ID: <1116434164.28096.9.camel@mcmanus.datapower.com> (raw)
In-Reply-To: <428B4D14.2030104@ammasso.com>

On Wed, 2005-05-18 at 10:11, Timur Tabi wrote:
> Given a particular file and a particular bitkeeper revision for the file, how can I tell 
> which version of the kernel incorporated that changeset?
> 
> In particular, I want to know about revision 1.65 of mm/rmap.c, which can be seen at 
> http://linux.bkbits.net:8080/linux-2.6/diffs/mm/rmap.c@1.65?nav=index.html|src/|src/mm|hist/mm/rmap.c
> 
> I want to know what the first version of Linux is to incorporate that change.
> 

The most pragmatic thing to do is to take the comment from the
changeset, which in this case is "mm: get_user_pages vs. try_to_unmap" 
and plop that into google as "changelog mm: get_user_pages vs.
try_to_unmap".. and that will point you very quickly to the right
release changelog that includes it, because the changelogs are generally
driven right from the comments.. in this case

 http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.7-rc3

While this isn't scientific - it has a very high success rate and is
easy as pi..



      parent reply	other threads:[~2005-05-18 16:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-18 14:11 linux.bkbits.net question: mapping cset to kernel version? Timur Tabi
2005-05-18 15:00 ` Hugh Dickins
2005-05-18 15:01   ` Timur Tabi
2005-05-18 15:14     ` Hugh Dickins
2005-05-18 16:09 ` Greg KH
2005-05-18 16:23   ` Timur Tabi
2005-05-18 16:51     ` Greg KH
2005-05-18 23:13       ` Linus Torvalds
2005-05-18 16:36 ` patrick mcmanus [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=1116434164.28096.9.camel@mcmanus.datapower.com \
    --to=mcmanus@ducksong.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.