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

Re: [PATCH] Teach git-svn how to catch up with its tracking branches

From
Steven Grimm <koreth@midwinter.com>
Date
May 8, 2008, 07:33 UTC
Message-ID
<CE2D2A30-CAAF-4903-95EA-B4577932B700@midwinter.com>
In-Reply-To
<alpine.DEB.1.00.0805072332300.6948@swallowtail>
On May 7, 2008, at 11:48 PM, Asheesh Laroia wrote:
Show 6 quoted lines
> The way I handle it is that, hidden somewhere, I have an account  
> with a cron job that does this:
>
> $ git svn fetch
> $ git push origin refs/remotes/*:refs/heads/*
> $ git push origin refs/remotes/trunk:refs/heads/master

That's a reasonable setup, and I think (without having tried it) that it will be compatible with my patch -- assuming the clones of your origin repository have appropriate svn-remote config entries, they should be able to mix and match fetching from your origin and the real svn repository, and dcommit stuff back to svn.

Though I'd try that out with a toy svn repo first...
-Steve
Previous: Asheesh LaroiaNext: Chris Shoemaker
Message 14 of 16 in “Teach git-svn how to catch up with its tracking branches”
  1. Teach git-svn how to catch up with its tracking branchesSteven Grimm, May 8, 2008
  2. Junio C HamanoMay 8, 2008
  3. Steven GrimmMay 8, 2008
  4. Chris ShoemakerMay 8, 2008
  5. Steven GrimmMay 8, 2008
  6. Chris ShoemakerMay 8, 2008
  7. Karl HasselströmMay 8, 2008
  8. Karl HasselströmMay 8, 2008
  9. Steven GrimmMay 8, 2008
  10. Karl HasselströmMay 8, 2008
  11. Teach git-svn how to catch up with its tracking branchesSteven Grimm, May 8, 2008
  12. Eric WongMay 11, 2008
  13. Asheesh LaroiaMay 8, 2008
  14. Steven GrimmMay 8, 2008
  15. Chris ShoemakerMay 8, 2008
  16. Chris ShoemakerMay 8, 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.