From: Achim Gratz <Stromeko@nexgo.de>
To: git@vger.kernel.org
Subject: Re: [PATCH] bisect: fix replay of CRLF logs
Date: Sun, 10 May 2020 12:54:43 +0200 [thread overview]
Message-ID: <87tv0o5abw.fsf@Rainer.invalid> (raw)
In-Reply-To: 20200509221730.GG7234@camp.crustytoothpaste.net
brian m. carlson writes:
> Cygwin allows configurable behavior for line endings, but I don't know
That's restricted to handling files in text mode based on a mount
option.
https://cygwin.com/faq.html#faq.api.cr-lf
> whether any configuration it allows handles CR in the shell. I'm sure
> Cygwin will do the right thing with LF only lines regardless, so it's
> probably safe to just assume LF-only behavior in the shell.
A handful of tools had patches to recognize and deal with CRLF in input,
but most of these patches have been dropped a long time ago. The better
assumption is that Cygwin behaves like Linux, so CR only input/output on
text.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2020-05-10 10:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 21:29 [PATCH] bisect: fix replay of CRLF logs Christopher Warrington via GitGitGadget
2020-05-07 22:13 ` Eric Sunshine
2020-05-07 22:25 ` Jeff King
2020-05-07 23:07 ` Junio C Hamano
2020-05-08 13:08 ` Jeff King
2020-05-08 15:07 ` Junio C Hamano
2020-05-08 16:28 ` Junio C Hamano
2020-05-08 17:12 ` Jeff King
2020-05-08 17:53 ` Junio C Hamano
2020-05-09 22:17 ` brian m. carlson
2020-05-10 10:54 ` Achim Gratz [this message]
2020-05-08 22:59 ` [EXTERNAL] " Christopher Warrington (CHRISTOPHER)
2020-05-09 16:28 ` Junio C Hamano
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=87tv0o5abw.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.