Re: [RFR] gitattributes(5) documentation
- From
- David Lang <david.lang@digitalinsight.com>
- Date
- Apr 22, 2007, 00:51 UTC
- Message-ID
- <Pine.LNX.4.63.0704211749300.5655@qynat.qvtvafvgr.pbz>
- In-Reply-To
- <7virbr4p0v.fsf@assigned-by-dhcp.cox.net>
On Thu, 19 Apr 2007, Junio C Hamano wrote:
Show 8 quoted lines
> Set to string value "input":: > > This is similar to setting the attribute to `true`, but > also forces git to act as if `core.autocrlf` is set to > `input` for the path. > > Any other value set to `crlf` attribute is ignored and git acts > as if the attribute is left unspecified.
I think that a better option would be that if it's set to a string value, that string value is treated as if core.autocrlf was set to that value.
in the long run this would let you phase out the core.autocrlf option entirely, letting the bahavior be specified in gitattributes.
David Lang