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

Re: gitweb showing slash r at the end of line

From
Ondra Medek <xmedeko@gmail.com>
Date
Jan 30, 2012, 07:55 UTC
Message-ID
<1327910140526-7235866.post@n2.nabble.com>
In-Reply-To
<201201281802.44339.jnareb@gmail.com>

Hi Jakub, I have read "SubmittingPatches". I have made a path by "git format-patch -M" and I have though it's enough. The problem maybe was, that I had not included "Subject: " from the result of "git format-patch -M". Next time I will try to do it better.

I am a Git newbie, but my bare repos have "config" file and this file can contain the "core.autocrlf" setting. So the gitweb can read it. Or what about to have a special section [gitweb] in this config? For now, the gitweb config files are somewhat "scattered" = "descrition", "cloneurl", "project.list", ...

Yeah, the autodetection of mixed mode line endings could be the best solution.

However, from my point of view a global gitweb setting would be enough for now.

-- View this message in context: http://git.661346.n2.nabble.com/gitweb-showing-slash-r-at-the-end-of-line-tp7229895p7235866.html Sent from the git mailing list archive at Nabble.com.

Previous: Jakub NarebskiNext: Jakub Narebski
Message 5 of 8 in “gitweb showing slash r at the end of line”
  1. Ondra MedekJan 27, 2012
  2. Jakub NarebskiJan 27, 2012
  3. Junio C HamanoJan 27, 2012
  4. Jakub NarebskiJan 28, 2012
  5. Ondra MedekJan 30, 2012
  6. Jakub NarebskiJan 30, 2012
  7. Ondra MedekJan 30, 2012
  8. Jakub NarebskiFeb 2, 2012

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.