From: Tom Rini <trini@kernel.crashing.org>
To: Wolfgang Denk <wd@denx.de>
Cc: linuxppc-dev@ozlabs.org,
linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: Kernel SCM saga..
Date: Wed, 6 Apr 2005 16:16:40 -0700 [thread overview]
Message-ID: <20050406231640.GJ3396@smtp.west.cox.net> (raw)
In-Reply-To: <20050406223751.E4297C108D@atlas.denx.de>
On Thu, Apr 07, 2005 at 12:37:46AM +0200, Wolfgang Denk wrote:
> Hi,
>
> are there any plans yet how to continue PPC kernel development now
> that Linus (and probably others, too) stopped using BitKeeper?
>
> See http://www.lib.uaa.alaska.edu/linux-kernel/archive/2005-Week-14/0826.html
Larely unchanged. The linuxppc-2.5 tree hasn't been active for a while,
so "official" trees shouldn't be a problem. I would hope/imagine that
whatever is picked up next will allow the sub-projects that've had
multiple colaborators (such as mpc52xx or marvell support) to work in
some fashion. For single-user stuff, I can't recommend quilt
(http://savannah.nongnu.org/projects/quilt) enough.
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2005-04-06 23:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-06 22:37 Kernel SCM saga Wolfgang Denk
2005-04-06 23:16 ` Tom Rini [this message]
2005-04-06 23:21 ` Eugene Surovegin
2005-04-06 23:33 ` Dan Malek
2005-04-07 0:13 ` Benjamin Herrenschmidt
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=20050406231640.GJ3396@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=wd@denx.de \
/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).