From: Dave Wolfe <dwolfe@lists.linuxppc.org>
To: Tom Gall <gall@rochcivictheatre.org>
Cc: linuxppc-dev@lists.linuxppc.org,
Rich Lafferty <rich@alcor.concordia.ca>,
David Edelsohn <dje@watson.ibm.com>
Subject: Re: https://sourceforge.net/projects/ppclinux/
Date: Sat, 10 Feb 2001 22:40:43 -0600 [thread overview]
Message-ID: <20010210224043.A10011@lists.linuxppc.org> (raw)
In-Reply-To: <3A85D80E.93FD01C9@rochcivictheatre.org>; from Tom Gall on Sat, Feb 10, 2001 at 06:08:46PM -0600
[ Tom Gall writes: ]
>
> Rich Lafferty wrote:
> >
> > There any chance of bug report updates going to a hypothetical
> > "linuxppc-bugs" rather than -dev?
>
> Seems like a reaonable approach... someone from lists.linuxppc.org
> wanna create it?
Ask an ye shall receive. I'll try to get to it in the next couple of
days. Do anyone know who to talk to at sourceforge to change where the
reports go? Does it need to be a restricted list or general discussion?
--
Dave Wolfe
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-11 4:40 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 ` https://sourceforge.net/projects/ppclinux/ Tom Gall
2001-02-11 4:40 ` Dave Wolfe [this message]
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=20010210224043.A10011@lists.linuxppc.org \
--to=dwolfe@lists.linuxppc.org \
--cc=dje@watson.ibm.com \
--cc=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).