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

Re: git-svn SVN 1.7 fix, take 2

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Jul 24, 2012, 22:02 UTC
Message-ID
<20120724220207.GA15969@burratino>
In-Reply-To
<500F17A3.60307@pobox.com>
Hi,
Michael G Schwern wrote:
> I'm trying to bust it up into easier to digest pieces.

I have a crazy idea. You might not like it, but maybe it's worth giving it a try.

[...]
> The Git::SVN extraction is more complicated than the rest, so I'll probably do
> that separately and bust it up into a few commits.

All of these changes are supposed to have zero functional effect, right?

Could you send the first five patches that *are* supposed to have a functional effect? I know that they will not apply cleanly to git-svn from git "master" or on top of each other; that's fine with me. If the approach looks right, interested people (read: probably Ben or I :)) can make the corresponding change in the code layout from "master". Afterwards, we can look into all that refactoring to make later changes easier.

What do you think?

Thanks, Jonathan

Previous: Jonathan NiederNext: Michael G Schwern
Message 5 of 14 in “git-svn SVN 1.7 fix, take 2”
  1. Michael G SchwernJul 24, 2012
  2. Junio C HamanoJul 24, 2012
  3. Michael G SchwernJul 24, 2012
  4. Jonathan NiederJul 24, 2012
  5. Jonathan NiederJul 24, 2012
  6. Michael G SchwernJul 24, 2012
  7. Jonathan NiederJul 24, 2012
  8. Jonathan NiederJul 24, 2012
  9. Junio C HamanoJul 24, 2012
  10. Michael G SchwernJul 25, 2012
  11. Jonathan NiederJul 25, 2012
  12. Michael G SchwernJul 25, 2012
  13. Junio C HamanoJul 25, 2012
  14. Michael G SchwernJul 25, 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.