From: Michael J Gruber <git@drmicha.warpmail.net>
To: Doki Pen <doki_pen@doki-pen.org>
Cc: git@vger.kernel.org
Subject: Re: git-svn fetch
Date: Fri, 29 May 2009 18:10:55 +0200 [thread overview]
Message-ID: <4A20090F.3070608@drmicha.warpmail.net> (raw)
In-Reply-To: <gvots5$uob$1@ger.gmane.org>
Doki Pen venit, vidit, dixit 29.05.2009 17:09:
> I'm sorry if this has been brought up before, I did look through the
> archive and didn't see it.
>
> I am working with a repo that has about 7000 commits and about 100
> branches/tags. I've been using git-svn for about 4 months now and love
> it. The problem I'm experiencing is that everytime a new branch is added,
> git svn fetch seems to download the entire history all the way from r1.
> Is this the expected behavior? If so, why is that? Don't we already have
> the old revisions from trunk and other branches?
>
AFAIK git-svn has to go back in order to search for possible earlier
history of $newbranch. For git-svn, the following two scenarios are
basically equivalent:
- a new branch is added to the svn repo
- you change your git-svn config so that a new branch becomes
"interesting" (which had been skipped before)
git-svn treats them the same way ("a branch we don't know about yet"),
because it can't really (reliably) distinguish between them.
Michael
next prev parent reply other threads:[~2009-05-29 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 15:09 git-svn fetch Doki Pen
2009-05-29 16:10 ` Michael J Gruber [this message]
2009-05-29 20:31 ` doki_pen
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=4A20090F.3070608@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=doki_pen@doki-pen.org \
--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.