From: Tom Gall <gall@rochcivictheatre.org>
To: linuxppc-dev@lists.linuxppc.org
Cc: Rich Lafferty <rich@alcor.concordia.ca>
Subject: Re: https://sourceforge.net/projects/ppclinux/
Date: Sat, 10 Feb 2001 18:08:46 -0600 [thread overview]
Message-ID: <3A85D80E.93FD01C9@rochcivictheatre.org> (raw)
In-Reply-To: 20010210185305.C7667@alcor.concordia.ca
Rich Lafferty wrote:
>
> On Sat, Feb 10, 2001 at 11:27:18AM -0600, Tom Gall (tom_gall@vnet.ibm.com) wrote:
> >
> > Hi All,
> >
> > This is reminder that for tracking bugs, patches etc, we have a really
> > nice facility at our finger tips and that is the PowerPC Linux project
> > on Sourceforge.net
> [...]
> > Last if you have a bug or what you think is a bug please report it via
> > this mechanism.
>
> There any chance of bug report updates going to a hypothetical
> "linuxppc-bugs" rather than -dev?
Hi Rich,
Seems like a reaonable approach... someone from lists.linuxppc.org
wanna create it?
--
Regards,
Tom
--------------------------------------------------------------
Linux Guy "My heart is human, my blood is boiling,
gall@rochcivictheatre.org my brain IBM" -- Mr Roboto, Styxx
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-11 0:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3A8579F6.4C5E97CD@vnet.ibm.com>
[not found] ` <Pine.LNX.4.21L.0102101430160.1671-100000@unix47.andrew.cmu.edu>
2001-02-10 21:01 ` BMAC stuff - what I have Joseph P. Garcia
2001-02-10 23:53 ` https://sourceforge.net/projects/ppclinux/ Rich Lafferty
2001-02-11 0:08 ` Tom Gall [this message]
2001-02-11 4:40 ` https://sourceforge.net/projects/ppclinux/ Dave Wolfe
2001-02-11 7:00 ` https://sourceforge.net/projects/ppclinux/ Tom Gall
2001-02-11 0:22 ` https://sourceforge.net/projects/ppclinux/ David Edelsohn
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=3A85D80E.93FD01C9@rochcivictheatre.org \
--to=gall@rochcivictheatre.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=rich@alcor.concordia.ca \
/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).