From: Mark Wielaard <mark@klomp.org>
To: Joshua Watt <JPEW.hacker@gmail.com>, bzip2-devel@sourceware.org
Subject: Re: [PATCH] Always treat .ref files as binary
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <2a06b1150e2c46156c39186bc815e4838849fb36.camel@klomp.org> (raw)
In-Reply-To: <20190702200601.27247-1-JPEW.hacker@gmail.com>
Hi Joshua,
On Tue, 2019-07-02 at 15:06 -0500, Joshua Watt wrote:
> .ref files should always be treated as binary files so that git does
> not attempt to convert the line endings if core.autocrlf is set.
I am not a big fan of autocrlf. I think it should just be left off.
But lets not make life miserable for people who do use it. Pushed.
Thanks,
Mark
prev parent reply other threads:[~2019-07-03 19:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 Joshua Watt
2019-01-01 0:00 ` Mark Wielaard [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=2a06b1150e2c46156c39186bc815e4838849fb36.camel@klomp.org \
--to=mark@klomp.org \
--cc=JPEW.hacker@gmail.com \
--cc=bzip2-devel@sourceware.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 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).