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
MOMatthew Ogilvie <mmogilvi_git@miniinfo.net>
Date
Nov 17, 2009, 03:59 UTC
Message-ID
<20091117035945.GA1728@comcast.net>
In-Reply-To
<20091116195048.6117@nanako3.lavabit.com>
On Mon, Nov 16, 2009 at 07:50:48PM +0900, Nanako Shiraishi wrote:
Show 8 quoted lines
> 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"?
>

I'm refering to the fact that the "crlf" section of Documentation/gitattributes.txt mentions core.autocrlf, which is in the opposite (reverse) direction as this new reference I'm adding.

The crlf section has a much more thorough description of the various knobs and settings and how they interact. But I just checked, and although the gitattributes crlf section describes core.autocrlf in reasonable detail, it does not have an actual link (reference?) to git-config or the core.autocrlf section. So the commit message isn't as clear as it could be.

Do I need to resubmit the patch, in order to rephrase the commit message?

-- Matthew Ogilvie [mmogilvi_git@miniinfo.net]

Previous: Nanako ShiraishiNext: Junio C Hamano
Message 3 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.