public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Carlo Florendo <subscribermail@gmail.com>
To: cygwin@cygwin.com
Subject: Re: bash-3.1-7^[$B!!^[(BBUG
Date: Mon, 18 Sep 2006 02:54:00 -0000	[thread overview]
Message-ID: <450E09EF.2080800@gmail.com> (raw)
In-Reply-To: <450E0880.9000401@gmail.com>

Carlo Florendo wrote:
> Larry Hall (Cygwin) wrote:
>>
>> I think this is getting a little off-track.  Another option just 
>> means another
>> area for people who don't understand what's going on to trip and fall 
>> and then
>> come and bug the list as a result.  IMO, there's already such an 
>> option, even
>> without changing bash.  It's called 'd2u'.  Let's not over-think and 
>> over-do
>> things here.  There's pain involved in that too.  I'm not convinced 
>> that it's
>> worth the pain to all for the benefit of a few.  Of course, I firmly 
>> believe
>> that what can and will be done here is Eric's call.  He's the one 
>> that will be
>> maintaining it.
>>
>
> You've got the keyverb:  overdo
>
> We've already got d2u.  There is a point in making bash scripts work 
> with CRLF endings but at the expense of a slower and a little bit 
> larger bash, I think.  (If I'm wrong here, I'm sorry, I haven't seen 
> bash's code.)
>
> d2u is much simpler.  For the sake of simplicity and elegance, let's 
> go d2u.
>
> Best Regards,
>
> Carlo
>
This was an old thread.  Sorry for the late reply.  I didn't check the 
dates.  

-- 
Carlo Florendo
Network Administrator
Astra Philippines Inc. (www.astra.ph)
Member of the Astra Group (www.astra.co.jp)


--
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-18  2:54 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                     ` Carlo Florendo [this message]
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                   ` bash-3.1-7^[$B!!^[(BBUG Christopher Faylor
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=450E09EF.2080800@gmail.com \
    --to=subscribermail@gmail.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).