From: Wolfgang Denk <wd@denx.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Dale Farnsworth <dale@farnsworth.org>, linuxppc-dev@lists.linuxppc.org
Subject: Re: MPC5200 Patches
Date: Mon, 17 Nov 2003 17:02:45 +0100 [thread overview]
Message-ID: <20031117160250.CD994C5F59@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 17 Nov 2003 08:19:48 MST." <20031117151948.GB30251@ip68-0-152-218.tc.ph.cox.net>
In message <20031117151948.GB30251@ip68-0-152-218.tc.ph.cox.net> you wrote:
>
> > > Per your suggestion above, I created
> > > bk://source.mvista.com/linuxppc_2_4_mpc5200
> >
> > Which source tree / change set is this based on?
>
> It's semi-moot. I've created a linux-2.4-mgt5100 tree, based off of
Can you please translate this into English for me?
My question was: is bk://source.mvista.com/linuxppc_2_4_mpc5200 base
on linuxppc_2_4 or linuxppc_2_4_devel, and which exact ChangeSet.
Why do you create a new tree ...-mgt5100 ? The MGT5100 can safely be
considered dead (except that ther eare some systems out there which
remain being supported),.
> Marcelo's tree to carefully check things into, and hopefully get him to
> pull from in 2.4.24-pre time-frame. I'll email everyone again once I've
> got it populated with stuff from Dale's tree.
Can you please explain the rationale behind creating a new source
tree? There is the old bk://source.mvista.com/linuxppc_2_4_mgt5100
tree, there is now Dave's new linuxppc_2_4_mpc5200 tree. There is
linux-2.4, linux-2.5, linuxppc_2_4_devel, linuxppc-2.4, linuxppc-2.5.
There is a couple other, less official source trees (like Ben's).
There is our CVS tree.
And instead of reducing the confusion about all the different kernel
source trees you created yet another one?? Why?
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
"It's like deja vu all over again." - Yogi Berra
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-11-17 16:02 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-01 9:36 MPC5200 Patches Wolfgang Denk
2003-11-03 23:31 ` Dale Farnsworth
2003-11-07 22:20 ` Wolfgang Denk
2003-11-10 19:02 ` Dale Farnsworth
2003-11-10 20:46 ` Wolfgang Denk
2003-11-10 21:00 ` Tom Rini
2003-11-12 0:34 ` Wolfgang Denk
2003-11-12 4:50 ` Dale Farnsworth
2003-11-12 9:30 ` Geert Uytterhoeven
2003-11-12 9:49 ` Wolfgang Denk
2003-11-12 9:59 ` Geert Uytterhoeven
2003-11-12 11:41 ` Gabriel Paubert
2003-11-12 11:51 ` Geert Uytterhoeven
2003-11-12 14:47 ` Wolfgang Denk
2003-11-12 14:45 ` Wolfgang Denk
2003-11-12 17:43 ` Gabriel Paubert
2003-11-12 19:41 ` Geert Uytterhoeven
2003-11-14 6:11 ` Kumar Gala
2003-11-14 15:20 ` Tom Rini
2003-11-12 15:18 ` Tom Rini
2003-11-12 15:49 ` Gary Thomas
2003-11-12 15:53 ` Tom Rini
2003-11-16 20:33 ` Wolfgang Denk
2003-11-17 6:07 ` Dale Farnsworth
2003-11-17 8:35 ` Wolfgang Denk
2003-11-17 15:19 ` Tom Rini
2003-11-17 16:02 ` Wolfgang Denk [this message]
2003-11-17 16:25 ` Tom Rini
2003-11-18 14:52 ` Dale Farnsworth
2003-11-20 11:53 ` Christoph Hellwig
2003-11-20 12:10 ` Wolfgang Denk
2003-11-20 12:17 ` Christoph Hellwig
2003-11-21 1:04 ` Paul Mackerras
2003-11-18 0:43 ` Benjamin Herrenschmidt
2003-11-18 0:44 ` Benjamin Herrenschmidt
2003-11-18 14:45 ` Wolfgang Denk
2003-11-18 15:00 ` Wolfgang Denk
2003-11-17 18:50 ` Tom Rini
2003-12-03 18:28 ` Dale Farnsworth
[not found] ` <20031203185310.19A48C5F5F@atlas.denx.de>
2003-12-04 0:35 ` Dale Farnsworth
[not found] ` <20031110162536.GC8584@ip68-0-152-218.tc.ph.cox.net>
2003-11-10 19:09 ` Dale Farnsworth
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=20031117160250.CD994C5F59@atlas.denx.de \
--to=wd@denx.de \
--cc=dale@farnsworth.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).