public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: cgf@cygnus.com (Christopher G. Faylor)
To: gnu-win32@cygnus.com
Subject: Re: Bug Report
Date: Thu, 02 Jul 1998 09:53:00 -0000	[thread overview]
Message-ID: <6ng8sv$r99$1@cronkite.cygnus.com> (raw)
In-Reply-To: <199807010655.IAA00527.cygnus.gnu-win32@surgery1.best.ms.philips.com>

In article <199807010655.IAA00527.cygnus.gnu-win32@surgery1.best.ms.philips.com>,
Ronald Pijnacker <Ronald.Pijnacker@best.ms.philips.com> wrote:
>....
>> To fix the most serious problems:
>>   Please, _READ_ the IMPORTANT UPGRADE NOTICE at the end of this note.
>>   Please, ensure that there is only _ONE_ cygwinb19.dll.
>>   Please, ensure that _ALL_ b18 binaries have been removed.
>>   Please, _USE_ the Searchable Mail Archives.
>....
>
>Wouldn't it be about time to release a new (or at least updated)
>version of the cygwin stuff? This would alow newcomers to start
>without having to upgrade their newly installed distrubution before
>they can do something useful. It would also eliminate the necessity
>for Earnie to keep on having to type `_READ_ the IMPORTANT UPGRADE
>NOTICE' etc. every time somebody asks a question about why something
>doesn't work.

You're right.  We'll probably be releasing a new version sometime after
Geoffrey returns from vacation.
-- 
cgf@cygnus.com             "Everything has a boolean value, if you stand
http://www.cygnus.com/      far enough away from it."  -- Galena Alyson Canada
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

  parent reply	other threads:[~1998-07-02  9:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <19980630141709.614.rocketmail@send101.yahoomail.com>
1998-07-01  8:02 ` Ronald Pijnacker
     [not found] ` <199807010655.IAA00527.cygnus.gnu-win32@surgery1.best.ms.philips.com>
1998-07-02  9:53   ` Christopher G. Faylor [this message]
     [not found] <CAJVfQ_gj3N5+j+NpJytcYqMnMVMj-_p=EuLKsZ7BwnYWNRMgJg@mail.gmail.com>
2023-09-06 22:20 ` bug report Asad Ali
2023-09-08  5:09   ` Brian Inglis
2022-02-08 22:01 Bug Report julie77793
2022-02-09  6:29 ` Ernie Rael
2022-02-09 16:24 ` Bill Stewart
  -- strict thread matches above, loose matches on Subject: below --
2003-05-05 16:21 Bug report Kern Sibbald
2003-05-05 16:38 ` Igor Pechtchanski
2003-05-05 17:14   ` Kern Sibbald
2003-05-05 17:30     ` Igor Pechtchanski
2003-05-05 17:33       ` Igor Pechtchanski
2003-05-05 16:40 ` Christopher Faylor
2001-06-06 22:21 David L Wiltshire
1997-02-17  8:27 bug report p.a.c.tavares
1997-02-16 22:10 Sean McNeil
1997-02-13  1:21 Sergey Okhapkin
1997-02-12 16:36 Andres Takach

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='6ng8sv$r99$1@cronkite.cygnus.com' \
    --to=cgf@cygnus.com \
    --cc=gnu-win32@cygnus.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).