[git-users] Re: Moving commits from one branch to another (or: My hassles with git-rebase)

[Stefan Schulze]

Hi,

just for the records:
John Keeping at g...@vger.kernel.org finally gave me the commands I was 
looking for:

 git rebase --onto svn pushedToSvn master^0
assembles the complete (pushedToSvn..master onto the commits at the 
svn-branch) history detached and
 git checkout -B svn HEAD
moved this to the svn-branch

-- 

Re: [git-users] Rebasing large commit-set including merges

[Stefan Schulze]

Hi Michael,

thank you for your answer. 
After playing with git grafts and git filter-tags according to your 
suggestion, it causes some different issues.
I think, I gave to less information about the situation, so I created a 
complete new thread (the root of the problem seems to be something 
different - I could solve the issue about the conflicts by calling a lot of 
git checkout. In that thread I posted my problem in a lot more details 
and with some examples.

Stefan

-- 

[git-users] Rebasing large commit-set including merges

[Stefan Schulze]

Hi,

I try to rebase our whole history (~1500 commits) onto a quite empty 
branch, only including a single commit (creating the base-directory - so 
there is nothing conflicting in there). I want to do this, because our 
project was developed on a git-repository but now we have to make our stuff 
available on a subversion-repository. So I created the target directory on 
subversion, added it with git svn init to my local git-repo and checked 
out a branch (git branch -b svn trunk). Now I want to add our commits to 
this branch to import it into the subversion-repository. (I don't want to 
add the single svn-commit to master, because I had to force-push master 
afterwards leading to lot's of trouble with already checked-out or local 
branches, I think)

After quite a lot of reading and try-and-failing with the arguments of 
git-rebase, I think, git checkout svn; git cherry-pick first-sha; git 
rebase -p --onto svn first-sha master is the correct way to go.
But when I call the rebase, I get lot's of conflicts I have to solve 
manually. It looks like these are the same conflicts, which where already 
solved in the various merge-commits in our history, so I'm confused why I 
have to solve all these conflicts again.

Can you tell me, where I missed something? If you know any smarter way to 
solve this task, I'd be happy to hear :)

Thanks in advance,
  Stefan Schulze

--