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

Re: [PATCH] Explain how svn-fe parses filenames in SVN dumps

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Apr 14, 2012, 18:18 UTC
Message-ID
<20120414181823.GB4560@burratino>
In-Reply-To
<4F89B5C5.3030606@pileofstuff.org>
Andrew Sayers wrote:
>                  For example, the handling of NUL characters is worse
> than newlines

Filenames are C strings. Filenames with NUL bytes simply do not exist, at least as long as one is using the ANSI C or POSIX interfaces for file access.

So as far as I can tell the story really is only about newlines. (If svn-fe tried to push history back to Subversion, life would presumably be more complicated.)

Hoping that clarifies a little, Jonathan

Previous: Jonathan NiederNext: Andrew Sayers
Message 5 of 7 in “Explain how svn-fe parses filenames in SVN dumps”
  1. Explain how svn-fe parses filenames in SVN dumpsAndrew Sayers, Apr 14, 2012
  2. Jonathan NiederApr 14, 2012
  3. Andrew SayersApr 14, 2012
  4. Jonathan NiederApr 14, 2012
  5. Jonathan NiederApr 14, 2012
  6. Andrew SayersApr 14, 2012
  7. Jonathan NiederApr 15, 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.