On Wed, May 28, 2003 at 07:14:37AM +0200, Sven Luther wrote: > On Tue, May 27, 2003 at 03:03:58PM -0700, Tom Rini wrote: > > On Mon, May 26, 2003 at 10:21:32PM +0200, Sven Luther wrote: > > > On Mon, May 26, 2003 at 09:06:24PM +0200, Sven Luther wrote: > > > > Hello, > > > > > > > > I am working on isolating the pop patches from the generic linuxppc > > > > patches. For this i need a 2.4.18-pre3 kernel from the ppc _devel tree. > > > > > > > > I suppose that this means the linux_2_4_devel tree. > > > > > > > > Anyway, i am not really all that familiar with bk, and could not find > > > > the information in the documentation. > > > > > > > > Could someone help me out and tell me how one can get, not the bk head, > > > > but an older revision ? Something equivalent to : > > > > > > > > cvs co -r 2.4.18-pre3 > > > > > > Ok, i found how to do it. > > > > > > BTW, is there a particular reason why bk tags have a v prepended to it, > > > (v2.4.18-pre3 instead of 2.4.18-pre3). > > > > Because it's 'version' 2.4.18-preX. But that's not what you wanted. > > You want v2.4.X_linuxppc_2_4_devel. Unfortunatly, I think these > > particular tags only go back as far as 2.4.19, and possibly only 2.4.20. > > Adding back-tags is on my todo list, but not very high. > > > > What you'll want to do is 'bk changes -e' and look for when v2.4.18-pre3 > > was merged into linuxppc_2_4, and then when that was merged into > > linuxppc_2_4_devel > > Err, if i have : > > $ bk changes -e > [EMAIL PROTECTED], 2002-01-10 14:46:59-07:00, [EMAIL PROTECTED] > patch-2.4.18-pre2-pre3 > TAG: v2.4.18-pre3 > > This does mean that i already have version v2.4.18-pre3, and that there > is a tag for it, and that you commited it ?
No. Tags identify how the source looks at the time the tag is issued in the tree it is issued. All v2.4.X tags are issued in the linux_2_4 tree, all v2.4.X_linuxppc_2_4 are in the linuxppc_2_4 tree and v2.4.X_linuxppc_2_4_devel are in the linuxppc_2_4_devel tree. > But then, maybe this is not what i search, since anyway, the pop 0.9.0 > patches, which supposedly work with 2.4.18-pre3 in the ppc _devel tree, > as said on the web pages, do not apply cleanly to it. Right. The v2.4.18-pre3 tag is for v2.4.18-pre3, as it appears in kernel.org. -- Tom Rini http://gate.crashing.org/~trini/
