From: Pazu <pazu@pazu.com.br>
To: git@vger.kernel.org
Subject: Re: core-git and porcelains
Date: Wed, 11 Oct 2006 14:13:33 -0300 [thread overview]
Message-ID: <egj8ot$eq6$1@sea.gmane.org> (raw)
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
next prev parent reply other threads:[~2006-10-11 17:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 14:39 core-git and porcelains Pazu
2006-10-11 15:08 ` Shawn Pearce
2006-10-11 16:45 ` Pazu
2006-10-11 16:54 ` Shawn Pearce
2006-10-11 17:13 ` Pazu [this message]
2006-10-11 17:01 ` Seth Falcon
2006-10-11 18:08 ` Robin Rosenberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='egj8ot$eq6$1@sea.gmane.org' \
--to=pazu@pazu.com.br \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.