From: msokolov@ivan.Harhan.ORG (Michael Sokolov)
To: linuxppc-dev@lists.linuxppc.org
Subject: linuxppc_2_4_alt started
Date: Sat, 30 Mar 02 21:58:33 PST [thread overview]
Message-ID: <0203310558.AA21170@ivan.Harhan.ORG> (raw)
Linux/PPC developers and users,
Having had no success in getting my work accepted into linuxppc_2_4_devel, I
have decided to start my own alternative tree which I have called
linuxppc_2_4_alt. The BK URL for anonymous access (should work, but I couldn't
really test access from outside) is:
bk://helium.Harhan.ORG:5000
This tree has linuxppc_2_4_devel as its BK parent. I have had this BK tree for
a while but I've just now made it publicly accessible. (The patches in my CVS
were generated from this tree with bk export -tpatch between the last cset
pulled from 2_4_devel and the very top cset.)
I have set it up to post to linuxppc-commit@source.mvista.com on incoming just
like the trees at BitMover. This way y'all will now what I'm doing in there and
see if you like it. If enough people like it maybe we'll take over. Anyone who
likes this tree, wants to do development in it, and wants read/write access
should contact me.
Have fun!
MS
P.S. It's on a 33.6 Kbps modem connection, so it's going to be *really* slow.
Any volunteers to host it for me on a machine with a better net connection? :-)
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-03-31 5:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-31 5:58 Michael Sokolov [this message]
2002-03-31 6:09 ` linuxppc_2_4_alt started Larry McVoy
2002-04-03 5:12 ` Troy Benjegerdes
2002-04-09 18:11 ` 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=0203310558.AA21170@ivan.Harhan.ORG \
--to=msokolov@ivan.harhan.org \
--cc=linuxppc-dev@lists.linuxppc.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).