public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: bash-3.1-7^[$B!!^[(BBUG
Date: Thu, 14 Sep 2006 02:07:00 -0000	[thread overview]
Message-ID: <20060914020737.GC24899@trixie.casa.cgf.cx> (raw)
In-Reply-To: <4508ABAF.5090408@scytek.de>

On Wed, Sep 13, 2006 at 06:09:03PM -0700, Volker Quetschke wrote:
>Christopher Faylor wrote:
>> On Wed, Sep 13, 2006 at 04:46:28PM -0700, Volker Quetschke wrote:
>(snip)
>> 
>>Do I have to make the observation again that whether this is the case
>>or not, it is not a primary goal of the Cygwin project to support these
>>people?
>
>Yes.  Did it ever cross your mind that the whole "Linux on Windows"
>thing is pretty useless if it cannot be used in the "real world".

Death of Cygwin predicted?  Everybody panic and/or sip?

>I mean, if people want to have a plain vanilla Linux thingy they can
>just install it.  Grab a Redhat, Suse or Debian DVD and everything
>works fine.

I suspect that the "Well, they can just install Linux (floppies, CDs,
DVDs) if they feel like it" observation has been made several times a
year for the last ten years.  It's obviously not a very powerful
argument since Cygwin is still here and you can't really assert that the
only reason it is here is because make understood MS-DOS paths or bash
dealt properly with \r\n line endings.

I doubt that Eric will want to deal with the fallout of having bash not
understand \r\n line endings but, if he does, it would be his decision
and, again, I would support it 100%.  I am very eager to see things like
configure scripts work faster and if we have to drop a few scared or
lazy people along the way to accomplish that goal, that's fine with me.
I have no problem at all with being a part of a smaller community which
doesn't need to use notepad to edit their bash scripts.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2006-09-14  2:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-13  4:38 bash-3.1-7^[$B!!^[(BBUG Eric Blake
2006-09-13  5:25 ` bash-3.1-7^[$B!!^[(BBUG Christopher Faylor
2006-09-13 14:33   ` bash-3.1-7^[$B!!^[(BBUG Eric Blake
2006-09-13 20:07     ` bash-3.1-7^[$B!!^[(BBUG Shankar Unni
2006-09-13 20:37       ` bash-3.1-7^[$B!!^[(BBUG mwoehlke
2006-09-13 21:48         ` bash-3.1-7^[$B!!^[(BBUG Eric Blake
2006-09-13 22:08           ` bash-3.1-7^[$B!!^[(BBUG mwoehlke
2006-09-13 23:46             ` bash-3.1-7^[$B!!^[(BBUG Volker Quetschke
2006-09-13 23:58               ` bash-3.1-7^[$B!!^[(BBUG David Rothenberger
2006-09-14  0:30                 ` bash-3.1-7^[$B!!^[(BBUG Larry Hall (Cygwin)
2006-09-18  2:48                   ` bash-3.1-7^[$B!!^[(BBUG Carlo Florendo
2006-09-18  2:54                     ` bash-3.1-7^[$B!!^[(BBUG Carlo Florendo
2006-09-14  0:19               ` bash-3.1-7^[$B!!^[(BBUG Christopher Faylor
2006-09-14  1:09                 ` bash-3.1-7^[$B!!^[(BBUG Volker Quetschke
2006-09-14  2:07                   ` Christopher Faylor [this message]
2006-09-14 11:13                     ` bash-3.1-7^[$B!!^[(BBUG Eric Blake
2006-09-14 16:58                       ` bash-3.1-7^[$B!!^[(BBUG Volker Quetschke
2006-09-14 17:15                         ` bash-3.1-7^[$B!!^[(BBUG Dave Korn
2006-09-14 17:22                           ` bash-3.1-7^[$B!!^[(BBUG Volker Quetschke
2006-09-14 17:26                         ` bash-3.1-7^[$B!!^[(BBUG Eric Blake
2006-09-21  3:50                         ` bash-3.1-7^[$B!!^[(BBUG Christopher Layne
2006-09-14 15:21                     ` bash-3.1-7 bug mwoehlke
2006-09-21  3:48                     ` bash-3.1-7^[$B!!^[(BBUG Christopher Layne
2006-09-21  3:37                 ` bash-3.1-7^[$B!!^[(BBUG Christopher Layne
  -- strict thread matches above, loose matches on Subject: below --
2006-09-13  4:13 bash-3.1-7^[$B!!^[(BBUG Eric Blake

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=20060914020737.GC24899@trixie.casa.cgf.cx \
    --to=cgf-no-personal-reply-please@cygwin.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).