On 1 January 2013 01:16, Sean Silva <silvas at purdue.edu> wrote:> I believe that what git-svn does is commit everything in your branch > that isn't in mainline (i.e. `origin/master..HEAD`). I don't think it > really pays any attention to branches (besides moving them after > committing).As if it was an SVN tree, makes sense.> Ok. I'll try to get to that today or tomorrow and CC you on the review thread.Thanks! -- cheers, --renato http://systemcall.org/
On Mon, Dec 31, 2012 at 6:20 PM, Renato Golin <rengolin at systemcall.org> wrote:>> I believe that what git-svn does is commit everything in your branch >> that isn't in mainline (i.e. `origin/master..HEAD`). I don't think it >> really pays any attention to branches (besides moving them after >> committing). > > As if it was an SVN tree, makes sense.I'm not sure if this was clear from my description, but it will still commit each commit in `origin/master..HEAD` individually. -- Sean Silva
On 1 January 2013 02:03, Sean Silva <silvas at purdue.edu> wrote:> I'm not sure if this was clear from my description, but it will still > commit each commit in `origin/master..HEAD` individually.Not explicitly, but I assumed so. Good thing git has a powerful squash/merge/reword interface. This is probably another topic that it's worth mention in the docs explicitly. -- cheers, --renato http://systemcall.org/