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

Re: How to rebase for git svn?

From
EWEric Wong <normalperson@yhbt.net>
Date
Nov 6, 2008, 09:55 UTC
Message-ID
<20081106095500.GA9587@untitled>
In-Reply-To
<4911EF4C.8030703@gmail.com>
Yang Zhang <yanghatespam@gmail.com> wrote:
Show 17 quoted lines
> Hi, I made a git svn repository from an svn repository.  Then I cloned  
> the git repository, committed some changes to the clone, and pulled back  
> to the original repository.  However, now the original repository gives  
> me conflicts whenever I run git svn rebase.  I believe this is because  
> git pull treats the other repository's commits as a branch and merges  
> them back instead of rebasing them and maintaining the type of linear  
> history that is good for playing with svn.  Any hints as to how to fix  
> this?  I think the solution is to undo the merge that resulted from the  
> pull, but I don't know how to do this.
>
> I wrote a simple script reproducing exactly what's going on (along with  
> a transcript of its output).  I tried to make it as simple as possible,  
> but it can probably be simplified even more to reproduce the problem:
>
> http://assorted.svn.sourceforge.net/viewvc/assorted/sandbox/trunk/src/git/gitsvn.bash?revision=1057&view=markup
>
> Thanks in advance for any help!
Hi,

Try passing --rebase or --squash with "git pull" to keep history linear for SVN.

-- 
Eric Wong
Previous: Yang ZhangNext: Sverre Rabbelier
Message 2 of 5 in “How to rebase for git svn?”
  1. Yang ZhangNov 5, 2008
  2. Eric WongNov 6, 2008
  3. Sverre RabbelierNov 6, 2008
  4. Björn SteinbrinkNov 6, 2008
  5. Yang ZhangNov 6, 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.