public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Michel LaBarre" <michel.labarre@rogers.com>
To: "'Soegtrop, Michael'" <michael.soegtrop@intel.com>,
	"'cygwin'" <cygwin@cygwin.com>
Subject: RE: 2.10.0: Cygwin now can not work well with a file in dos format.
Date: Sat, 16 Jun 2018 20:34:00 -0000	[thread overview]
Message-ID: <000a01d40585$b742e1f0$25c8a5d0$@rogers.com> (raw)
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A17788014D3@IRSMSX102.ger.corp.intel.com>

Thank you for the thoughtful responses Michael and Marco.

I am sorting through the references from both of you while trying to keep in mind
all the caveats regarding mount mode, file-path syntax ( /d/zot vs d:\zot ), and whether
any given utility is "line" oriented or not to infer how it might or might not hardwire the open mode.
(BTW, Section 3.2.1 of the user guide may need an update wrt sed ...)

I don't question the decisions - just trying to understand the implications before I next update everything.

The issue of text vs binary open must regularly boost alcohol sales.

(Note to self:  do not skip messages with [ANNOUNCEMENT] in the subject.)

Thanks
/Michel



--
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:[~2018-06-16 15:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15 16:19 tuyanyi
2018-06-15 19:46 ` Soegtrop, Michael
2018-06-15 23:50   ` cyg Simple
2018-06-16  0:49   ` Brian Inglis
2018-06-16 14:10   ` Michel LaBarre
2018-06-16 15:21     ` Marco Atzeri
2018-06-16 20:25     ` Soegtrop, Michael
2018-06-16 20:34       ` Michel LaBarre [this message]
2018-06-17  1:13       ` cyg Simple
2018-06-15 22:50 ` cyg Simple

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='000a01d40585$b742e1f0$25c8a5d0$@rogers.com' \
    --to=michel.labarre@rogers.com \
    --cc=cygwin@cygwin.com \
    --cc=michael.soegtrop@intel.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).