From: "Jurko Gospodnetić" <jurko.gospodnetic@docte.hr>
To: git@vger.kernel.org
Subject: [PATCH] Updated the Documentation/config.txt core.autocrlf configuration setting documentation
Date: Mon, 28 Jul 2008 13:48:14 +0200 [thread overview]
Message-ID: <g6kbm1$gbp$1@ger.gmane.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
Hi all.
This is just a fix for something in the documentation that confused
me when playing around with git.
--- Comment: --------
Updated the Documentation/config.txt core.autocrlf configuration
setting documentation to note that this setting can be set at a
repository or file level by using the gitattributes configuration.
Signed-off-by: Jurko <jurko.gospodnetic@docte.hr>
---------------------
Diff is attached as a separate file.
Still have not figured out how to best send in patches (working on
Windows here) so this one is a manually sent mail and you will most
likely not be able to apply it automatically. :-(
I am also not sure whether there are perhaps any other documentation
copies that need to be updated for this. This was the only one I found
in the source tree.
Best regards,
Jurko Gospodnetić
[-- Attachment #2: config.txt.patch --]
[-- Type: text/plain, Size: 875 bytes --]
diff --git a/Documentation/config.txt b/Documentation/config.txt
index 1a13abc..d9c1401 100644
--- a/Documentation/config.txt
+++ b/Documentation/config.txt
@@ -135,9 +135,10 @@ core.autocrlf::
writing to the filesystem. The variable can be set to
'input', in which case the conversion happens only while
reading from the filesystem but files are written out with
- `LF` at the end of lines. Currently, which paths to consider
- "text" (i.e. be subjected to the autocrlf mechanism) is
- decided purely based on the contents.
+ `LF` at the end of lines. Which paths to consider "text" (i.e. be subjected
+ to the autocrlf mechanism) will be decided based on the contents but this
+ can be overruled on a per-repository or per-file level by using
+ linkgit:gitattributes[5].
core.safecrlf::
If true, makes git check if converting `CRLF` as controlled by
reply other threads:[~2008-07-28 11:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='g6kbm1$gbp$1@ger.gmane.org' \
--to=jurko.gospodnetic@docte.hr \
--cc=git@vger.kernel.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.