linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Bethe <dan_bethe@yahoo.com>
To: linuxppc-dev@lists.linuxppc.org, jhaas@linuxppc.org, jcarr@linuxppc.org
Subject: Re: the state of the linuxppc-dev community
Date: Tue, 8 Feb 2000 17:35:09 -0800 (PST)	[thread overview]
Message-ID: <20000209013509.18757.qmail@web1006.mail.yahoo.com> (raw)



> Except that the server is never current, yes.  The _only_ place right now
> with any sort of current sources is in bitkeeper trees.  So once bk is
> released, things should look a bit better.

	Hi, Tom.  Freshmeat.net tells me that bitkeeper at
http://www.bitmover.com/bitkeeper/.  This is the official maintenance tool for
the generic Linux kernel, right?  If I understand you correctly, it sounds like
LinuxPPC is moving to bitkeeper as well, once bitkeeper 1.0 is out.
	Does this mean that the intermediary unofficial LinuxPPC-specific code will be
also located on the same Bitkeeper server as the generic kernel all the way?
So that even if there is some PPC code that is not [yet] community-tested and
Linus-approved, we will still check it out from an alternate "line of
development" on the same bitkeeper server?
	It sounds to me like, in general, bitkeeper intends to supercede or obsolete
CVS.
	Thanks for the info.  And many thanks to everyone who's responded today.  This
is the kind of cooperation we're looking for.  Gabe and I are going to take the
facts that everyone's painstakingly outlined (thanks, BenH) and make unifying
docs, to be served from linuxppc.org, hopefully to everyone's approval.
	We were also planning on setting up a CVS server for linuxppc.org, but I'm
gathering that that is unnecessary due to the upcoming use of bitkeeper.  Any
confirmation or comments on that?
	We'll still make sure that linuxppc.org has a good internal server setup, and
to help manage the userspace stuff even better.  We can install a bugtracking
system.  I've only extensively used GNATS, but I'm thinking about trying
Bugzilla (www.bugzilla.org) at my current workplace.
	And finally, I'm glad people responded positively and optimistically.  That's
my main attitude.  Within an hour, I got at least 5 private responses that
basically say "Amen".  Just like each of the several times I've already sent
out varying degrees of interrogation observation to the linuxppc.org community.
	I don't ever mean to be harsh, no matter how many non-positives I may ever
point out to anyone about anything.  We just need for the bazaar to be less
bizarre  ;-)

=====
"Don't expect your own messiah; this neverworld which you desire is
only in your mind." -- http://www.dreamtheater.net/songb4.htm#IV5

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-02-09  1:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-09  1:35 Dan Bethe [this message]
     [not found] <20000209100229.B5973@linuxcare.com>
2000-02-09 20:04 ` the state of the linuxppc-dev community Michael Schmitz
2000-02-09 22:14 ` Tom Rini
  -- strict thread matches above, loose matches on Subject: below --
2000-02-09 17:19 Jan Nieuwenhuizen
     [not found] <20000209014216.17047.qmail@web1001.mail.yahoo.com>
2000-02-09  9:22 ` Larry McVoy
     [not found] <20000208233505.29535.qmail@web1003.mail.yahoo.com>
2000-02-09  0:09 ` Tom Rini
2000-02-09 11:30 ` Michael Schmitz
2000-02-08 23:37 Dan Bethe
2000-02-09  0:13 ` Tony Mantler
2000-02-09  0:26   ` Tom Rini
2000-02-09  0:46     ` Larry McVoy
2000-02-09  0:51       ` Tom Rini
2000-02-09  1:02         ` Larry McVoy

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=20000209013509.18757.qmail@web1006.mail.yahoo.com \
    --to=dan_bethe@yahoo.com \
    --cc=jcarr@linuxppc.org \
    --cc=jhaas@linuxppc.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).