From: Pazu <pazu@pazu.com.br>
Date: Wed, 11 Oct 2006 17:13:33 GMT
Subject: Re: core-git and porcelains
Message-ID: <egj8ot$eq6$1@sea.gmane.org>
In-Reply-To: <20061011165403.GC31298@spearce.org>

Shawn Pearce wrote:

> I don't use multiple upstream branches in SVN fortunately, but the
> git-svn documentation suggests there is a way to change the Git
> branch name from 'refs/remotes/git-svn' to another name such that
> you can create one Git branch for each remote SVN branch.  Of course
> you need to set that environment variable before invoking git-svn.

I was reading git-svn documentation and just found about multi-init. 
Seems like you're describing, execept that no branch get init'ed as the 
"default" branch, and you always need to specify the the branch name 
before doing a fetch/dcomic/etc. I hope this works for me -- I'll need 
to switch between two or three remote branches quite frequently.

> As for my daily work with git-svn, I run "git svn fetch" to fetch any
> changes that had occurred in SVN along the branch I follow, then if
> any changes did exist I merge them into my Git working branch with
> "git pull . refs/remotes/git-svn".  When I'm ready to send stuff
> back up to SVN I do "git svn dcommit refs/remotes/git-svn..master",
> where master is the name of the Git branch I want to send.

Sounds a lot like what I do today with svk. If git works for me just as 
good as svk, the speed increase alone will make the switch worth.

-- Marcus