From: Michel Dänzer <daenzerm@student.ethz.ch>
To: Tom Gall <gall@rochcivictheatre.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Patches, Bugs etc ..
Date: Mon, 07 Aug 2000 08:29:28 +0200 [thread overview]
Message-ID: <398E5748.10E48750@student.ethz.ch> (raw)
In-Reply-To: 398DADDF.61D21A9E@rochcivictheatre.org
Tom Gall wrote:
> I've created a project on Source Forge with the idea that it would be
> perfect for tracking bugs, patches, projects and so on based on the
> conversations that were going on here a couple of days ago.
>
> Located at: http://sourceforge.net/projects/ppclinux/ or
> https://sourceforge.net/projects/ppclinux/ if you are
> logged in
>
> The facilities are here for CVS, releasing files, forums, mailing
> lists, support requests etc etc. Sourceforge does alot. I turned off
> CVS, forums, mailing lists etc as these are things that are already
> being done in the PowerPC Linux community and I didn't think there was
> any need for the duplication of effort unless maybe someday there is
> desire to change over.
>
> Hopefully this is a good thing and I certainly welcome your input. If
> there are others that would like to pitch in and help with this that'd
> be great.
We've also started a SourceForge project (called linux-apus) some months ago
for everything APUS, and our experience has been good so far. APUS development
has come to a new life, and the SourceForge folks are very supportive.
Michel
--
If the box says `Windows 95 or better'', it should run on Linux, right?
______________________________________________________________________________
Earthling Michel Dänzer (MrCooper) \ CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \ member of XFree86, Team *AMIGA*, AUGS
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-08-07 6:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-06 18:26 Patches, Bugs etc Tom Gall
2000-08-07 6:29 ` Michel Dänzer [this message]
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=398E5748.10E48750@student.ethz.ch \
--to=daenzerm@student.ethz.ch \
--cc=gall@rochcivictheatre.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).