linuxppc_2_4_devel tree and 2.4.19

linuxppc_2_4_devel tree and 2.4.19

[Tim M. Sanders]

I have the latest linuxppc_2_4_devel tree from
bk://source.mvista.com/linuxppc_2_4_devel.  I wanted to get the 2.4.19 "release"
out of the tree.  I do bk clone -rv2.4.19 linuxppc_2_4_devel linuxppc_2419.  I
know that the directory arch/ppc/platforms is suppose to be part of the 2.4.19
tree, but it is not in the cloned tree.  What am I doing wrong?


--
--
===========================
Tim M. Sanders
Synergy Microsystems
520.690.1709 x323

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: linuxppc_2_4_devel tree and 2.4.19

[Tom Rini]

On Tue, Oct 29, 2002 at 11:47:12AM -0700, Tim M. Sanders wrote:
>
> I have the latest linuxppc_2_4_devel tree from
> bk://source.mvista.com/linuxppc_2_4_devel.  I wanted to get the 2.4.19 "release"
> out of the tree.  I do bk clone -rv2.4.19 linuxppc_2_4_devel linuxppc_2419.  I
> know that the directory arch/ppc/platforms is suppose to be part of the 2.4.19
> tree, but it is not in the cloned tree.  What am I doing wrong?

v2.4.19 is kernel.org, as of 2.4.19, not the tree as of 2.4.19.  Do a
'bk changes', and look at where linuxppc_2_4 of the time was merged into
linuxppc_2_4_devel.

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: linuxppc_2_4_devel tree and 2.4.19

[Tim M. Sanders]

Thanks, that worked.  My misunderstanding.

On Tue, Oct 29, 2002 at 12:20:59PM -0700, Tom Rini wrote:
>
> On Tue, Oct 29, 2002 at 11:47:12AM -0700, Tim M. Sanders wrote:
> >
> > I have the latest linuxppc_2_4_devel tree from
> > bk://source.mvista.com/linuxppc_2_4_devel.  I wanted to get the 2.4.19 "release"
> > out of the tree.  I do bk clone -rv2.4.19 linuxppc_2_4_devel linuxppc_2419.  I
> > know that the directory arch/ppc/platforms is suppose to be part of the 2.4.19
> > tree, but it is not in the cloned tree.  What am I doing wrong?
>
> v2.4.19 is kernel.org, as of 2.4.19, not the tree as of 2.4.19.  Do a
> 'bk changes', and look at where linuxppc_2_4 of the time was merged into
> linuxppc_2_4_devel.
>
> --
> Tom Rini (TR1265)
> http://gate.crashing.org/~trini/
>

--
--
===========================
Tim M. Sanders
Synergy Microsystems
520.690.1709 x323

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: linuxppc_2_4_devel tree and 2.4.19

[Tom Rini]

On Wed, Oct 30, 2002 at 01:53:46AM -0800, Chris Zimman wrote:

> I'm just learning BitKeeper now -- and have a similar question.  I want
> to get the 2.4.19 (or 2.4.18, etc.) version of the kernel, but with all
> the enhancements for the Walnut platform (eg. OCP ethernet, PCI support,
> etc.)
>
> What I've been doing is cloning with -rv2.4.19, but as you pointed out,
> I think that gets me the kernel.org 2.4.19.  I'm clearly confused on how
> the merging works with respect to the mainline tree.

Basically a tag, like v2.4.19 works in BK in a similar way to CVS.  It
is the state of _a_ tree when that patch was applied.  But unlike CVS,
that tree can be pulled into another tree (somewhat like merging
branches, but only for thinking the problem out).  After this merge
happens however, no symbolic tag is made in the next tree.

So, to track down when a tag made in the linux_2_4 tree was merged into
the linuxppc_2_4 tree, you have to do a 'bk changes' and look by hand,
or a bk sccstool (graphical) and look at each ChangeSet.  This is
similar to the process for linuxppc_2_4_devel, except you want to see
when then linuxppc_2_4 tree, which had just had the linux_2_4 tree of
the version you want, was merged into linuxppc_2_4_devel.

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/