From: Tom Rini <trini@kernel.crashing.org>
To: "Tim M. Sanders" <tsanders@synergymicro.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: linuxppc_2_4_devel tree and 2.4.19
Date: Tue, 29 Oct 2002 12:20:59 -0700 [thread overview]
Message-ID: <20021029192059.GI688@opus.bloom.county> (raw)
In-Reply-To: <20021029114712.J25527@evilcat.ioinc.tucson.az.us>
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/
next prev parent reply other threads:[~2002-10-29 19:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-29 18:47 linuxppc_2_4_devel tree and 2.4.19 Tim M. Sanders
2002-10-29 19:20 ` Tom Rini [this message]
2002-10-29 20:00 ` Tim M. Sanders
[not found] ` <20021030095346.GA16076@mail.cryptoapps.com>
2002-10-30 14:10 ` Tom Rini
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=20021029192059.GI688@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=tsanders@synergymicro.com \
/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.