From: Andrei Rybak <rybak.a.v@gmail.com>
To: "Duy Nguyen" <pclouds@gmail.com>, "Torsten Bögershausen" <tboegi@web.de>
Cc: Robert Dailey <rcdailey.lists@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Automatic core.autocrlf?
Date: Mon, 27 Aug 2018 19:32:08 +0200 [thread overview]
Message-ID: <94afe154-53e1-761a-4a66-4f77188036f7@gmail.com> (raw)
In-Reply-To: <CACsJy8Bik2Hokgv46ifsFhhvGzdcB=FoWnWs6_k2361s15wOPA@mail.gmail.com>
On 2018-08-27 17:52, Duy Nguyen wrote:
> On Mon, Aug 27, 2018 at 5:37 PM Torsten Bögershausen <tboegi@web.de> wrote:
>>> 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.
>>
>
> An alternative is supporting conditional config includes based on
> platform or host name, but I don't know if there are more use cases
> like this to justify it.
>
How about just using unconditional includes?
global.gitconfig (synced across machines):
[include]
path = platform-specific.gitconfig
And two version of file named "platform-specific.gitconfig", which
are not synced, and include only code.autocrlf setting.
--
Best regards, Andrei R.
next prev parent reply other threads:[~2018-08-27 17:32 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
2018-08-27 15:52 ` Duy Nguyen
2018-08-27 17:29 ` Robert Dailey
2018-08-27 17:32 ` Andrei Rybak [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=94afe154-53e1-761a-4a66-4f77188036f7@gmail.com \
--to=rybak.a.v@gmail.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=rcdailey.lists@gmail.com \
--cc=tboegi@web.de \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).