public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: DJ Delorie <dj@delorie.com>
To: jik@curl.com
Cc: cygwin@cygwin.com
Subject: Re: cygwin and GPL (again)
Date: Thu, 15 Feb 2001 07:52:00 -0000	[thread overview]
Message-ID: <200102151552.KAA31074@envy.delorie.com> (raw)
In-Reply-To: <20010215140905.27743.qmail@lizard.curl.com>

> After reading the descriptions of the cygwin and cygwin-developers
> list, I got the distinct impression that I don't belong on the
> cygwin-developers list.

Perhaps it's time to reconsider the purposes of the lists?  I would be
happy to treat the cygwin-developer list as appropriate for any topic
about the internals or improvement of the cygwin runtime or support
files (including documentation, and people interested in learning
about the internals for the purposes of porting to cygwin), and leave
the cygwin list for people who are just using the runtime, without
interest in how it works.  The DJGPP lists work like this.

The cygwin-apps list would then be for people to discuss the porting
of apps to cygwin, when it doesn't involve knowing too much about the
internals of the cygwin runtime itself.  We should expect crossover
anyway, but it's easier to be lenient than try to define the
boundaries of the lists too precisely.

As for keeping things on-topic, it's easy enough to politely say "this
discussion belongs on [foo], please move it there" (if it's a faq,
along with an answer, if possible ;) than to start holy wars about
list topics.

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2001-02-15  7:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-14 12:48 Newsgroup? Andreas Madritsch
2001-02-14 13:25 ` Newsgroup? Christopher Faylor
2001-02-14 14:32   ` Newsgroup? Andreas Madritsch
2001-02-14 18:23   ` cygwin and GPL (again) David Case
2001-02-14 18:55     ` Bradley Bell
2001-02-14 19:18       ` Charles Wilson
2001-02-14 19:51         ` Bradley Bell
2001-02-14 20:00           ` Christopher Faylor
2001-02-14 19:14     ` Dennis McCunney
2001-02-14 19:36       ` Christopher Faylor
2001-02-14 20:15         ` DJ Delorie
2001-02-14 20:25         ` Dennis McCunney
2001-02-14 20:29           ` Christopher Faylor
2001-02-14 20:50             ` Dennis McCunney
2001-02-14 21:00               ` Christopher Faylor
2001-02-14 21:34                 ` Dennis McCunney
2001-02-15 13:19                   ` Rank Newbie Qustion [Was: Re: cygwin and GPL (again)] David A. Cobb
2001-02-15 14:30                     ` Christopher Faylor
2001-02-15  1:27                 ` cygwin and GPL (again) Jesper Eskilson
2001-02-15  6:09                   ` Jonathan Kamens
2001-02-15  7:52                     ` DJ Delorie [this message]
2001-02-15  9:40                   ` 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=200102151552.KAA31074@envy.delorie.com \
    --to=dj@delorie.com \
    --cc=cygwin@cygwin.com \
    --cc=jik@curl.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).