From: "Björn Steinbrink" <B.Steinbrink@gmx.de>
To: Bob Cotton <bob.cotton@rallydev.com>
Cc: git@vger.kernel.org
Subject: Re: git svn rebase does not follow new svn tags and branches
Date: Tue, 1 Apr 2008 23:05:21 +0200 [thread overview]
Message-ID: <20080401210521.GA20422@atjola.homenet> (raw)
In-Reply-To: <m28wzx5me4.fsf@rallydevelopment.com>
On 2008.04.01 14:51:47 -0600, Bob Cotton wrote:
>
> I've been using git-svn for several weeks. After replaying svn using
> git-svn clone and git-svn fetch, all branches and tags were replicated
> in the git repo.
>
> Now, after a workflow that includes git-svn rebase, but no git-svn
> fetch(s), the new svn tags and branches are not being replicated.
git svn rebase only fetches the revisions that are required to do the
rebase, which speeds the process up quite a bit. Imagine you're working
on branch "foo" and trunk is quite active. If git svn rebase would
always fetch all the new revisions for trunk as well (which you might
not need right now), that could become quite annoying.
If you want all remote branches/tags (incl. trunk) to be updated, use
git svn fetch.
Björn
prev parent reply other threads:[~2008-04-01 21:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 20:51 git svn rebase does not follow new svn tags and branches Bob Cotton
2008-04-01 21:05 ` Björn Steinbrink [this message]
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=20080401210521.GA20422@atjola.homenet \
--to=b.steinbrink@gmx.de \
--cc=bob.cotton@rallydev.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox