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

git-svn, merging et al.

From
Nigel Magnay <nigel.magnay@gmail.com>
Date
May 16, 2008, 15:50 UTC
Message-ID
<320075ff0805160850r473582d9qc33f71ba7f56dd51@mail.gmail.com>
Ok - it's Friday and I've got to interact with svn again..

I'm using git-svn, and I've not followed the guidance. Development has gone on in git branches and merges - but now I need to commit the changes back into svn, and dcommit is, understandably, not very happy.

I'm intending to instead do something like a
  git format-patch svn-branch..git-branch
  git checkout svn-branch
... apply all the patches ...
  git commit
  git svn dcommit
  # back to the git work
  git checkout git-branch
  # this shouldn't have to do merging - but it will have the parents
to make it clear where the last merge happened from ?
  git merge svn-branch

I'm happy that I'm bludgeoning changes in one big blob into SVN, as I can reasonably say 'if you want the real details, go look at gitweb)

I've tried doing this with
 git checkout svn-branch
 git merge --squash git-branch
But I don't get the result I'm expecting - what have I missed?
Next: Kevin Ballard
Message 1 of 3 in “git-svn, merging et al.”
  1. Nigel MagnayMay 16, 2008
  2. Kevin BallardMay 16, 2008
  3. Nigel MagnayMay 19, 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.