From: Wolfgang Denk <wd@denx.de>
To: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Kernel SCM saga..
Date: Thu, 07 Apr 2005 00:37:46 +0200 [thread overview]
Message-ID: <20050406223751.E4297C108D@atlas.denx.de> (raw)
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
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Far back in the mists of ancient time, in the great and glorious days
of the former Galactic Empire, life was wild, rich and largely tax
free. - Douglas Adams, _The Hitchhiker's Guide to the Galaxy_
next reply other threads:[~2005-04-06 22:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-06 22:37 Wolfgang Denk [this message]
2005-04-06 23:16 ` Kernel SCM saga Tom Rini
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=20050406223751.E4297C108D@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@ozlabs.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).