From: Jeff King <peff@peff.net>
To: "Kelly F. Hickel" <kfh@mqsoftware.com>
Cc: Hannu Koivisto <azure@iki.fi>, git@vger.kernel.org
Subject: Re: CRLF support bugs (was: Re: .gitattributes glob matchingbroken)
Date: Tue, 4 Nov 2008 22:07:03 -0500 [thread overview]
Message-ID: <20081105030702.GD20907@coredump.intra.peff.net> (raw)
In-Reply-To: <63BEA5E623E09F4D92233FB12A9F79430296676E@emailmn.mqsoftware.com>
On Tue, Nov 04, 2008 at 06:37:27AM -0600, Kelly F. Hickel wrote:
> From my point of view, the factoid that a particular file should be
> subjected to having its line endings munged is a _project_ decision.
> Whether or not to munge them on any given platform is a _local_
> decision.
Now that you spell it out, I am reminded that that is the argument I
remember having seen in past discussions. And of course, that argues for
.gitattributes being carried by the project, but the core.autocrlf
_config_ being a local decision.
Which, perhaps not coincidentally, is how it is currently implemented. :)
-Peff
prev parent reply other threads:[~2008-11-05 3:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-02 16:33 .gitattributes glob matching broken Hannu Koivisto
2008-11-03 9:09 ` Jeff King
2008-11-03 15:05 ` CRLF support bugs (was: Re: .gitattributes glob matching broken) Hannu Koivisto
2008-11-03 15:25 ` CRLF support bugs Hannu Koivisto
2008-11-03 16:46 ` CRLF support bugs (was: Re: .gitattributes glob matching broken) Dmitry Potapov
2008-11-03 22:24 ` CRLF support bugs Hannu Koivisto
2008-11-04 5:14 ` CRLF support bugs (was: Re: .gitattributes glob matching broken) Jeff King
2008-11-04 12:37 ` CRLF support bugs (was: Re: .gitattributes glob matchingbroken) Kelly F. Hickel
2008-11-05 3:07 ` Jeff King [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=20081105030702.GD20907@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=azure@iki.fi \
--cc=git@vger.kernel.org \
--cc=kfh@mqsoftware.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