git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Doc: mention the crlf attribute in config autocrlf section

From
Nanako Shiraishi <nanako3@lavabit.com>
Date
Nov 16, 2009, 10:50 UTC
Message-ID
<20091116195048.6117@nanako3.lavabit.com>
In-Reply-To
<1258223700-4009-1-git-send-email-mmogilvi_git@miniinfo.net>
Quoting Matthew Ogilvie <mmogilvi_git@miniinfo.net>
> The reverse reference has long existed, and the autocrlf description
> was actually obsolete and wrong (saying only file content is used),
> not just incomplete.
What do you mean by "reverse reference"?
Show 23 quoted lines
> Signed-off-by: Matthew Ogilvie <mmogilvi_git@miniinfo.net>
> ---
>  Documentation/config.txt |    7 ++++---
>  1 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/config.txt b/Documentation/config.txt
> index d1e2120..0dc6b12 100644
> --- a/Documentation/config.txt
> +++ b/Documentation/config.txt
> @@ -169,9 +169,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.  A file is considered
> +	"text" (i.e. be subjected to the autocrlf mechanism) based on
> +	the file's `crlf` attribute, or if `crlf` is unspecified,
> +	based on the file's contents.  See linkgit:gitattributes[5]. 
>  
>  core.safecrlf::
>  	If true, makes git check if converting `CRLF` as controlled by
The updated text looks correct to me.
-- 
Nanako Shiraishi
http://ivory.ap.teacup.com/nanako3/
Previous: Matthew OgilvieNext: Matthew Ogilvie
Message 2 of 5 in “Doc: mention the crlf attribute in config autocrlf section”
  1. Doc: mention the crlf attribute in config autocrlf sectionMatthew Ogilvie, Nov 14, 2009
  2. Nanako ShiraishiNov 16, 2009
  3. Matthew OgilvieNov 17, 2009
  4. Junio C HamanoNov 17, 2009
  5. Matthew OgilvieNov 17, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.