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

Re: git-svn merge helper

From
Benoit SIGOURE <tsuna@lrde.epita.fr>
Date
Sep 30, 2007, 14:15 UTC
Message-ID
<1EF130A4-3CC7-4A42-9166-3539D9A38828@lrde.epita.fr>
In-Reply-To
<20070930110550.GA4557@atjola.homenet>
On Sep 30, 2007, at 1:05 PM, Björn Steinbrink wrote:
Show 13 quoted lines
> Hi,
>
> I recently discovered git-svn and absolutey love it. One thing that  
> I'm
> missing though, is an equivalent of "svn merge" for merging between  
> svn
> remotes, to support the SVN way of using "squashed" merges, where you
> just note the merge meta-data in the commit message. "git merge"  
> didn't
> work for me (and probably isn't expected to work) to merge between two
> svn branches, so I've resorted to cherry-picking the required commits
> one by one into a temporary branch and then squashing them together by
> doing a --squash merge with a second temporary branch (as in [1]).

I fail to see why you'd want to reproduce the broken behavior of svn merge. Anyways, git-svn is a great way to merge SVN branches, unfortunately it can't detect when merges happened on the SVN side. I think you can use it nevertheless by manually adding a graft at the last merge point, which would help you merging the right revisions without having to specify what needs to be merged (unless someone made another merge on the SVN side, in which case you need to update your graft).

Cheers,
-- 
Benoit Sigoure aka Tsuna
EPITA Research and Development Laboratory
Previous: Björn SteinbrinkNext: Björn Steinbrink
Message 2 of 10 in “git-svn merge helper”
  1. Björn SteinbrinkSep 30, 2007
  2. Benoit SIGOURESep 30, 2007
  3. Björn SteinbrinkOct 1, 2007
  4. Benoit SIGOUREOct 1, 2007
  5. Björn SteinbrinkOct 2, 2007
  6. Steven WalterOct 2, 2007
  7. Björn SteinbrinkOct 2, 2007
  8. Steven WalterOct 3, 2007
  9. Björn SteinbrinkOct 3, 2007
  10. Andreas EricssonOct 3, 2007

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.