From: David Edelsohn <dje@watson.ibm.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: https://sourceforge.net/projects/ppclinux/
Date: Sat, 10 Feb 2001 19:22:20 -0500 [thread overview]
Message-ID: <200102110022.TAA25668@mal-ach.watson.ibm.com> (raw)
In-Reply-To: Message from Rich Lafferty <rich@alcor.concordia.ca> of "Sat, 10 Feb 2001 18:53:05 EST." <20010210185305.C7667@alcor.concordia.ca>
>>>>> Rich Lafferty writes:
Rich> Is there any chance of bug report updates going to a hypothetical
Rich> "linuxppc-bugs" rather than -dev?
Yes! I completely agree. I personally find the sourceforge
autofeed to linuxppc-dev to be quite annoying. A separate list to track
the bug reports to which developers acn subscribe separately is exactly
what is needed.
Thanks, David
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-02-11 0:22 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 ` https://sourceforge.net/projects/ppclinux/ Dave Wolfe
2001-02-11 7:00 ` https://sourceforge.net/projects/ppclinux/ Tom Gall
2001-02-11 0:22 ` David Edelsohn [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=200102110022.TAA25668@mal-ach.watson.ibm.com \
--to=dje@watson.ibm.com \
--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).