From: Mike Frysinger <vapier@gentoo.org>
To: linux-sh@vger.kernel.org
Subject: Re: For those interested in the Dreamcast
Date: Mon, 12 Jan 2009 12:53:34 +0000 [thread overview]
Message-ID: <200901120753.36361.vapier@gentoo.org> (raw)
In-Reply-To: <1231703328.6478.4.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 2385 bytes --]
On Monday 12 January 2009 03:40:08 Paul Mundt wrote:
> On Mon, Jan 12, 2009 at 08:16:54AM +0000, Adrian McMenamin wrote:
> > On Mon, 2009-01-12 at 16:54 +0900, Paul Mundt wrote:
> > > On Sun, Jan 11, 2009 at 07:48:48PM +0000, Adrian McMenamin wrote:
> > > > Veterans of the Dreamcast development community will recall we used
> > > > to have a pretty good general mailing list, but it long ago fell into
> > > > disuse.
> > > >
> > > > I know the community is much smaller now than before but it would be
> > > > good to have a general list, so I have set one up. Please consider
> > > > subscribing
> > > >
> > > > http://transpero.net/cgi-bin/mailman/listinfo/dreamcastdev
> > >
> > > Please explain how more fragmentation in this area is going to help
> > > anything. It seems like you are aiming for one mailing list per
> > > dreamcast developer.
> > >
> > > Any OS specific stuff needs to go through the port-specific list, and
> > > architecture specific issues can be cross-posted across those as well.
> > > The only thing a dreamcast-specific list would be useful for would be
> > > discussions of native development on bare metal that people don't see a
> > > good fit for anywhere else. However, even that stuff is likely marginal
> > > enough at this point that there is no reason to discourage such threads
> > > from popping up on the OS-specific lists.
> > >
> > > When you are already suffering from lack of activity due to your
> > > platform being in its death throes, more mailing list fragmentation is
> > > definitely not the answer.
> >
> > If you don't want to subscribe that is up to you.
> >
> > In the meantime this is not further fragmentation but the opposite - an
> > attempt to (once again) have a single point where cross-OS issues could
> > be discussed.
>
> You seem to have entirely missed the point about cross-posting being OK
> for these situations today. The linux-sh list is certainly open to
> cross-posting, regardless of whether people are subscribed or not, and
> general architectural issues are certainly best discussed there.
if people cant be bothered to find all the relevant lists, how about you
(Adrian) create an alias that simply expands to all the relevant lists ?
a quick glance at netbsd archives indicates that the sh3/dreamcast lists see
very little traffic anyways ...
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2009-01-12 12:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 19:48 For those interested in the Dreamcast Adrian McMenamin
2009-01-12 7:54 ` Paul Mundt
2009-01-12 8:16 ` Adrian McMenamin
2009-01-12 8:40 ` Paul Mundt
2009-01-12 12:53 ` Mike Frysinger [this message]
2009-01-12 13:16 ` Adrian McMenamin
2009-01-13 7:38 ` Peter Bortas
2009-01-13 9:51 ` Adrian McMenamin
2009-01-28 0:36 ` Peter Bortas
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=200901120753.36361.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=linux-sh@vger.kernel.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