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

Re: gitweb and unicode special characters

From
Edward Z. Yang <edwardzyang@thewritingpot.com>
Date
Dec 13, 2008, 03:06 UTC
Message-ID
<ghv8rf$47v$1@ger.gmane.org>
In-Reply-To
<200812130231.06929.jnareb@gmail.com>
Jakub Narebski wrote:
> Sidenote: There is probably one exception we want to add, namely not
> escape '\r' at the end of line, to be able to deal better with DOS
> line endings (\r\n).

I'm sorry, but I have to disagree. I find being able to see \r line-endings in the pretty-printed format is exceedingly useful for figuring out if a file has been checked in with the wrong line-endings. The number of files that must have \r line endings are vanishingly small (Bat files are perhaps the one example I can think of right now).

Cheers, Edward

Previous: Jakub NarebskiNext: Jakub Narebski
Message 6 of 7 in “gitweb and unicode special characters”
  1. Praveen ADec 12, 2008
  2. Jakub NarebskiDec 12, 2008
  3. Jakub NarebskiDec 12, 2008
  4. Praveen ADec 13, 2008
  5. Jakub NarebskiDec 13, 2008
  6. Edward Z. YangDec 13, 2008
  7. Jakub NarebskiDec 13, 2008

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.