public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: DJ Delorie <dj@delorie.com>
To: jsturm@sigma6.com
Cc: jgrishaw@onebox.com, cygwin@sourceware.cygnus.com
Subject: Re: Cygwin snapshots (was: Re: PLEASE help with V1.0 canonical mode problem
Date: Tue, 28 Mar 2000 12:55:00 -0000	[thread overview]
Message-ID: <200003282053.PAA19995@envy.delorie.com> (raw)
In-Reply-To: <38E11A6B.DAE7A504@sigma6.com>

> I take that to mean "don't use a snapshot in place of the release
> unless you have a good reason", like comm support, ntsec, etc.
> Sorta common sense, I think...

The wording is designed for people who don't have common sense.  We
don't worry about the ones that do.

> What does it mean to "support" the CD anyway?

In the case of the Cygwin CD, it means that we help you (via email or
phone to one of our support people, not via this mailing list) get the
software installed and running.  It also means that the code base is
more stable than average.

> I'm not too familiar with Cygwin development... is there a ChangeLog
> file?

Yes.

> What about a "cygwin-patches" list?

Yes, but only recently, when we moved development to CVS on
sourceware.

> Do Cygwin developers use regression testing?  Is there are test suite
> available?

We only recently added the ability to run a testsuite against cygwin
(it's in winsup/cygwin/testsuite) but so far nobody has contributed
any tests.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

      reply	other threads:[~2000-03-28 12:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-28 10:39 James Grishaw
2000-03-28 12:43 ` Cygwin snapshots (was: " Jeff Sturm
2000-03-28 12:55   ` DJ Delorie [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=200003282053.PAA19995@envy.delorie.com \
    --to=dj@delorie.com \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=jgrishaw@onebox.com \
    --cc=jsturm@sigma6.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).