From: linux-dev <linux-dev@dialectique.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] gentoo ppc
Date: Thu, 4 Apr 2002 13:14:04 +0200 [thread overview]
Message-ID: <20020404131404.759dfbe2.linux-dev@dialectique.org> (raw)
In-Reply-To: <200204011336.g31Da2D10753@excalibur.skynet.be>
> does anyone think a separate gentooppc (announce/dev) mailinglist is needed?
YES! the testing/bugs/error reports will most likely have a lot of
ppc specific causes. to avoid putting a burden on the gentoo-dev or
gentoo-user lists, i'd recommend a gentoo-ppc list. this has worked
successfully before (at least with debian-ppc).
/r
next prev parent reply other threads:[~2002-04-04 11:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-25 12:34 [gentoo-dev] gentoo ppc Pieter Van den Abeele
2002-03-25 13:03 ` Kain
2002-03-25 13:59 ` Pieter Van den Abeele
2002-03-29 8:53 ` Kain
2002-03-29 9:24 ` Pieter Van Den Abeele
2002-03-30 2:57 ` Kain
2002-03-30 19:01 ` Pieter Van den Abeele
2002-03-31 3:42 ` Fuper
2002-04-01 12:12 ` Pieter Van den Abeele
2002-04-01 14:29 ` Pieter Van den Abeele
2002-04-04 11:14 ` linux-dev [this message]
2002-04-04 11:03 ` [gentoo-dev] ppc mailinglist Bjarke Sørensen
[not found] <20020107190114.C377053@plato.zk3.dec.com>
2002-01-08 15:45 ` [gentoo-dev] gentoo ppc Debian User Jean-Baptiste Note
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=20020404131404.759dfbe2.linux-dev@dialectique.org \
--to=linux-dev@dialectique.org \
--cc=gentoo-dev@gentoo.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