From: Junio C Hamano <junkio@cox.net>
To: David Lang <david.lang@digitalinsight.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>, git@vger.kernel.org
Subject: Re: [RFR] gitattributes(5) documentation
Date: Sun, 22 Apr 2007 00:02:06 -0700 [thread overview]
Message-ID: <7vmz10q4cx.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0704211749300.5655@qynat.qvtvafvgr.pbz> (David Lang's message of "Sat, 21 Apr 2007 17:51:57 -0700 (PDT)")
David Lang <david.lang@digitalinsight.com> writes:
> in the long run this would let you phase out the core.autocrlf option
> entirely, letting the bahavior be specified in gitattributes.
You _could_, but that is quite against what we want. These
should stay separate, and the gitattributes mechanism is
designed specifically to allow them cleanly separated.
The configuration "core.autcrlf" describes a particular
repository. If the platform the repository is on expects text
files to be line-terminated with CRLF, you would have
core.autocrlf set; otherwise you don't.
On the other hand, gitattributes' 'crlf' describes if the path
is text, and that is the reason it can and should be "in-tree",
i.e. not just $GIT_DIR/info/attributes (which is private to the
repository) but in .gitattributes (and subdirectories'), which
is given to everybody who has a copy of the project.
How text files are handled is a local matter, and stays in the
config. Which ones are text is the same for everybody who has a
copy of the project, and is in-tree information.
next prev parent reply other threads:[~2007-04-22 7:02 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 8:17 What's cooking in git.git (topics) Junio C Hamano
2007-04-16 1:53 ` Junio C Hamano
2007-04-19 0:04 ` Junio C Hamano
[not found] ` <7vslav4yv6.fsf_ -_@assigned-by-dhcp.cox.net>
2007-04-19 0:23 ` Alex Riesen
2007-04-19 2:39 ` Nicolas Pitre
2007-04-19 10:07 ` Martin Waitz
2007-04-20 11:14 ` Junio C Hamano
2007-04-20 11:58 ` Alex Riesen
2007-04-20 19:31 ` Sam Ravnborg
2007-04-21 6:09 ` Martin Waitz
2007-04-21 7:11 ` Linus Torvalds
2007-04-20 1:29 ` [RFR] gitattributes(5) documentation Junio C Hamano
2007-04-20 1:45 ` Linus Torvalds
2007-04-20 5:02 ` Junio C Hamano
2007-04-22 0:51 ` David Lang
2007-04-22 7:02 ` Junio C Hamano [this message]
2007-04-22 9:33 ` David Lang
2007-04-20 1:57 ` Nicolas Pitre
2007-04-22 6:24 ` What's cooking in git.git (topics) Junio C Hamano
2007-04-23 7:04 ` Junio C Hamano
2007-04-23 16:16 ` Nicolas Pitre
2007-04-23 17:07 ` Alex Riesen
2007-04-23 17:15 ` Junio C Hamano
2007-04-23 21:16 ` Alex Riesen
2007-04-23 21:51 ` Junio C Hamano
2007-04-24 15:58 ` Alex Riesen
2007-04-24 16:04 ` Johannes Schindelin
2007-04-24 16:14 ` Alex Riesen
2007-04-24 16:44 ` Johannes Schindelin
2007-04-24 21:41 ` Junio C Hamano
2007-04-25 8:11 ` Alex Riesen
2007-04-23 17:25 ` Johannes Schindelin
2007-04-27 8:24 ` Junio C Hamano
2007-04-29 18:33 ` Junio C Hamano
2007-04-29 18:45 ` Linus Torvalds
2007-04-30 23:20 ` Junio C Hamano
2007-05-06 8:53 ` Junio C Hamano
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=7vmz10q4cx.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=david.lang@digitalinsight.com \
--cc=git@vger.kernel.org \
--cc=torvalds@linux-foundation.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.
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).