public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Roger Krebs <Roger.Krebs@stage-entertainment.com>
To: David Macek <david.macek.0@gmail.com>,
	"cygwin@cygwin.com"	<cygwin@cygwin.com>
Subject: AW: when using cygwin version 2.8.2 the behavior of CR/LF changed completely compared to previous versions
Date: Thu, 03 Aug 2017 12:47:00 -0000	[thread overview]
Message-ID: <DB6PR0601MB2085AF3A70102475ABB9B0A5BAB10@DB6PR0601MB2085.eurprd06.prod.outlook.com> (raw)
In-Reply-To: <860bf833-674f-1e8c-4165-35e36376480e@gmail.com>

Hi,

I've seen that there were some changes regarding CR/LLF in sed and cygcheck, but I havn't recognized that several other tool has also changed their behavior in the past. We haven't done an update for a longer period of time (why update when anything runs well) and therefor now we've been faced with several similar changes in the behavior of different tools. That's the reason why we've thought that this must be something general.

Many thanks to bring me into the right context. We've made some smaller changes in our scripts and everything seems to work fine now.

Again many thanks for the very quick and helpful response.

Best Regards
Roger Krebs

-----Ursprüngliche Nachricht-----
Von: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] Im Auftrag von David Macek
Gesendet: Mittwoch, 2. August 2017 17:46
An: cygwin@cygwin.com
Betreff: Re: when using cygwin version 2.8.2 the behavior of CR/LF changed completely compared to previous versions

On 2. 8. 2017 17:34, Roger Krebs wrote:
> Hi,
> 
> after updating from version 1.7.33 to version 2.8.2 the behavior of CR-LF handling completely changed. This results in several srcipt errors etc.

See announcements:

* <https://cygwin.com/ml/cygwin-announce/2017-02/msg00036.html> for sed
* <https://cygwin.com/ml/cygwin-announce/2017-02/msg00035.html> for grep
* <https://cygwin.com/ml/cygwin-announce/2017-02/msg00034.html> for gawk

There was also a discussion about these changes at <https://cygwin.com/ml/cygwin/2017-06/msg00040.html>.

-- 
David Macek


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


      reply	other threads:[~2017-08-03 12:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02 15:34 Roger Krebs
2017-08-02 15:46 ` David Macek
2017-08-03 12:47   ` Roger Krebs [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=DB6PR0601MB2085AF3A70102475ABB9B0A5BAB10@DB6PR0601MB2085.eurprd06.prod.outlook.com \
    --to=roger.krebs@stage-entertainment.com \
    --cc=cygwin@cygwin.com \
    --cc=david.macek.0@gmail.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).