From: Andrew DeFaria <Andrew@DeFaria.com>
To: cygwin@cygwin.com
Subject: Re: Why not a news server?
Date: Tue, 05 Feb 2002 16:19:00 -0000 [thread overview]
Message-ID: <3C607683.6060201@DeFaria.com> (raw)
In-Reply-To: <20020206000517.GA12007@redhat.com>
Christopher Faylor wrote:
>On Tue, Feb 05, 2002 at 03:30:25PM -0800, Andrew DeFaria wrote:
>
>>News servers were created exactly to address this issue. It is the
>>medium developed exactly for what we are trying to do here. Am I so
>>wrong to ask why we are not using the medium?!?.
>>
>As a wild guess, I suppose because a newsgroup isn't available?
>
>If you feel this strongly about a news server then I see no reason why
>you shouldn't set one up. I'll be happy to advertise the service on
>the cygwin web site.
>
>I'd suggest that you gateway the cygwin mailing list into news, and
>vice versa. That would probably be optimum.
>
>I have several other great ideas which I'll be happy to share with you
>once you've gotten your service set up.
>
>cgf
>
As I just got through mentioning to Larry I would take a shot at setting
it up however I lack the resources (a machine, the software and the
space). Hosting this from my home PC is probably not a good idea.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-02-06 0:19 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 15:30 Andrew DeFaria
2002-02-05 15:43 ` Larry Hall (RFK Partners, Inc)
2002-02-05 16:05 ` Christopher Faylor
2002-02-05 16:19 ` Andrew DeFaria [this message]
2002-02-05 17:44 ` Christopher Faylor
2002-02-05 16:35 ` James Potts (Arek)
2002-02-05 17:35 ` Christopher Faylor
2002-02-17 5:39 ` Per Abrahamsen
2002-02-17 15:52 ` Daniel Adams
2002-02-17 17:57 ` Christopher Faylor
2002-02-19 15:47 ` Christopher Faylor
2002-03-02 14:29 ` Christopher Faylor
2002-03-02 14:46 ` Daniel Adams
2002-03-02 14:50 ` Christopher Faylor
2002-03-02 15:07 ` Charles Wilson
2002-03-02 15:10 ` Daniel Adams
2002-03-02 15:20 ` Lars Magne Ingebrigtsen
2002-03-02 15:31 ` Daniel Adams
2002-03-02 15:33 ` Charles Wilson
2002-03-02 16:02 ` Andrew DeFaria
2002-03-02 16:30 ` Charles Wilson
2002-03-02 16:33 ` Lars Magne Ingebrigtsen
2002-03-02 16:45 ` Charles Wilson
2002-03-02 18:38 ` Andrew DeFaria
2002-03-02 19:07 ` Christopher Faylor
2002-03-02 14:58 ` Randall R Schulz
2002-02-18 9:27 ` Andrew DeFaria
-- strict thread matches above, loose matches on Subject: below --
2002-02-18 10:53 Randall R Schulz
2002-02-18 14:32 ` Andrew DeFaria
2002-02-01 9:59 Andrew DeFaria
2002-02-01 10:20 ` Randall R Schulz
2002-02-01 10:26 ` Daniel Adams
2002-02-01 10:48 ` Peter Buckley
2002-02-01 10:28 ` Larry Hall (RFK Partners, Inc)
2002-02-01 12:29 ` Stephano Mariani
2002-02-01 13:25 ` Larry Hall (RFK Partners, Inc)
[not found] ` <4.3.1.2.20020201143046.01cb6770@pop.ma.ultranet.com>
2002-02-01 12:49 ` Andrew DeFaria
2002-02-01 13:15 ` Larry Hall (RFK Partners, Inc)
2002-02-01 13:33 ` Greg Mosier
2002-02-01 13:37 ` Robert Collins
2002-02-01 20:05 ` Greg Mosier
2002-02-01 13:48 ` Charles Wilson
2002-02-01 20:10 ` Greg Mosier
2002-02-01 20:48 ` Charles Wilson
2002-02-01 13:31 ` Christopher Faylor
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=3C607683.6060201@DeFaria.com \
--to=andrew@defaria.com \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).