search for: tocommit

...ypick work or is the merging process going to confuse > git-svn? To use git-svn you should always have a history without any git merges. Just commit after commit after commit. I do not know what kind of history git-cherrypick produces. I would do the cherrypicking like this: git checkout -b toCommit git rebase -i HEAD~30 > Remove all the unneeded commits in the upcoming window git svn -n dcommit // Check what would be committed git svn dcommit // Commit Cheers Tobi

Rafael Ávila de Espíndola <rafael.espindola at gmail.com> writes: > On 07/05/2011 03:27 PM, David Greene wrote: >> My git-svn fu is not very strong. >> >> In the course of preparing a set of AVX patches, I've committed several >> changes to my local LLVM git clone. I don't want to send all of those >> changes upstream right away. What's the

...w what kind > of history git-cherrypick produces. To clarify, I just need to create the branch at the point just before the first commit to go to upstream. Are merges in the history before that point going to be a problem? > I would do the cherrypicking like this: > > git checkout -b toCommit > git rebase -i HEAD~30 Ok, I'll try something like that. >> Remove all the unneeded commits in the upcoming window > > git svn -n dcommit // Check what would be committed > git svn dcommit // Commit Ok, thanks. git-svn is a bit awkward, so thanks everyone for your help!...