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
ASAndrew Sayers <andrew-git@pileofstuff.org>
Date
Apr 14, 2012, 21:56 UTC
Message-ID
<4F89F27B.5050706@pileofstuff.org>
In-Reply-To
<20120414181823.GB4560@burratino>
On 14/04/12 19:18, Jonathan Nieder wrote:
> 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.)

I think I've been trying to balance two incompatible use cases - ordinary users that just need a heads-up about a bug that might bite them, and authors of related tools (i.e. me) that need technical information about svn-fe.

I think your text serves ordinary users better, so I'll investigate pushing history back to Subversion tomorrow and think how to write something more technical. I'm afraid my patch etiquette fails me here though - is it better for me to roll your text into a new patch, or let you do that and submit my text separately?

	- Andrew
Previous: Jonathan NiederNext: Jonathan Nieder
Message 6 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.