From: "Torsten Bögershausen" <tboegi@web.de>
To: Robert Dailey <rcdailey.lists@gmail.com>
Cc: Git <git@vger.kernel.org>
Subject: Re: Automatic core.autocrlf?
Date: Mon, 27 Aug 2018 17:35:24 +0200 [thread overview]
Message-ID: <20180827153524.GA18025@tor.lan> (raw)
In-Reply-To: <CAHd499APYCH2r2=+M_AGKUzN0GDmrwDty4wK=Xy-utCdMrd56w@mail.gmail.com>
On Mon, Aug 27, 2018 at 09:10:33AM -0500, Robert Dailey wrote:
> Is there an 'auto' setting for the 'core.autocrlf' config? Reason I
> ask is, I want that setting to be 'input' on linux but 'true' on
> Windows. I have a global .gitconfig that I sync across different
> platforms with Google Drive, and I hate to manage 2 copies of it on
> each platform (linux and Windows). If there's some way to make the
> line ending configuration the same between both, that would be
> awesome.
>
> Note that I do rely mostly on git attributes files for this, however
> not all upstream repositories have one, and I don't always have
> permission to create one there.
How many repos do you look at, and how big is the "pain level" here?
Would it be possible to submit pull-requests ?
> In those cases, when it falls back to
> configuration for line ending management, I want it to be
> automatically configured based on the host platform.
There is
git config core.eol native
But that is already the default, and it needs the 'text' attribute
to be set (or auto), the simplest solution is to have
* text=auto
in .gitattributes
>
> Any advice is appreciated here. Unfortunately Google isn't much help
> on this topic, Stack Overflow is a swamp full of different information
> and none of it seems authoritative.
Out of interest, not to blame anybody:
Did you ever look at
https://git-scm.com/docs/git-config
The authoritative answer is in the Git project itself,
under Documentation/config.txt
In summary, if I understand you right,
the solution would be to use .gitattributes in every project.
HTH
next prev parent reply other threads:[~2018-08-27 15:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 14:10 Automatic core.autocrlf? Robert Dailey
2018-08-27 15:35 ` Torsten Bögershausen [this message]
2018-08-27 15:52 ` Duy Nguyen
2018-08-27 17:29 ` Robert Dailey
2018-08-27 17:32 ` Andrei Rybak
2018-08-27 18:22 ` Andrei Rybak
2018-08-28 0:14 ` brian m. carlson
2018-08-30 14:53 ` Robert Dailey
2018-08-30 4:54 ` Jonathan Nieder
2018-08-30 14:57 ` Robert Dailey
2018-08-30 18:56 ` Torsten Bögershausen
2018-08-30 19:10 ` Randall S. Becker
2018-08-31 3:29 ` Jonathan Nieder
2018-08-31 11:57 ` Randall S. Becker
2018-08-31 13:17 ` Torsten Bögershausen
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=20180827153524.GA18025@tor.lan \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=rcdailey.lists@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 NNTP newsgroup(s).