Date: Wed, 18 May 2005 16:13:01 -0700 (PDT)
From: Linus Torvalds <torvalds@osdl.org>
To: Greg KH <greg@kroah.com>
cc: Timur Tabi <timur.tabi@ammasso.com>, linux-kernel@vger.kernel.org
Subject: Re: linux.bkbits.net question: mapping cset to kernel version?
In-Reply-To: <20050518165148.GC17307@kroah.com>
Message-ID: <Pine.LNX.4.58.0505181544360.18337@ppc970.osdl.org>
References: <428B4D14.2030104@ammasso.com> <20050518160930.GA16756@kroah.com>
 <428B6BF8.2010303@ammasso.com> <20050518165148.GC17307@kroah.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1371
Lines: 43


On Wed, 18 May 2005, Greg KH wrote:
> > What does he do now?
> 
> Uses git, which will have the same issues as you are facing :)

Both git and BK can do this.

Once you know which commit you want to check, the way to find out what the
first release was that contained that commit is perfectly straightforward:  
you take each release, and see if the commit is reachable from that
release. You don't need to actually look at the patches, it's enough to
look at the revision tree.

In Git, you can basically do something like

	for i in $releases
	do
		j=$(git-merge-base $commit $i)
		if [ "$j" == "$commit" ]; then
			echo $commit was in $i
		fi
	done

where "releases" is the list of SHA1 names for the commits of the releases
you're interested in, and "commit" is the SHA1 name of the commit you're 
looking at.

In BK, you can do similar things with "bk cset" (and there's some other
helper things for it too), but I don't have the docs available any more,
so..

In all fairness, usually it _is_ easier to just do a grep for it if you 
already have the release patches available. It's what I usually did 
myself.

		Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/