From: Hin-Tak Leung <hintak.leung@gmail.com>
To: git@vger.kernel.org
Subject: git svn's performance on cloning mono's branches/tags...
Date: Fri, 26 Jun 2009 01:39:35 +0100 [thread overview]
Message-ID: <3ace41890906251739r45b3eae9oe1b7e32886defc0f@mail.gmail.com> (raw)
(I'm not on list so please CC) - I am trying to git svn clone mono's
repository, and for some strange reason it is doing a complete check
out from revision 1 all the way to each branch/tag . Is this normal or
am I doing anything wrong? I have git svn clone a few other things
recently (R, ghostscript) and I don't remember git doing this, but R
is quite a normal svn layout and I think I only have ghostcript trunk
(no branch/tag).
What I did was this: I started out with just git-svn clone trunk
(which generated the first two [now-commented out] lines), then I
thought I also want 2.4 branch so I added the next commented-out
section, and ran 'git svn fetch --all'. Then I thought I like the
whole thing - so I commented out most of it and added the 4 lines as
blow - which is also my current git config.
The problem is that it seems to treat every tag as a branch, and also
seem to want to check out every revision from r1 up to r3382 for
MONO_0_10, etc.
to mono/tags/MONO_0_10@3382 , and r1 to r2598 for mono/tags/MONO_0_9@2598 , etc.
--------------------------------------------------------------------
[svn-remote "svn"]
# url = svn://anonsvn.mono-project.com/source/trunk/mono
# fetch = :refs/remotes/git-svn
url = svn://anonsvn.mono-project.com/source
tags = tags/*/mono:refs/remotes/mono/tags/*
branches = branches/*/mono:refs/remotes/mono/branches/*
trunk = trunk/mono:refs/remotes/git-svn
#[svn-remote "mono24"]
# url = svn://anonsvn.mono-project.com/source/branches/mono-2.4/mono
# fetch = :refs/remotes/git-svn-mono24
--------------------------------------------------------------------
I guess my ultimate question is, how does one modify git config to
track tags and branches, etc as well, *after* having already svn
clone'd trunk?, without burning too much bandwidth?
next reply other threads:[~2009-06-26 0:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 0:39 Hin-Tak Leung [this message]
2009-06-26 5:15 ` git svn's performance on cloning mono's branches/tags Andreas Ericsson
2009-06-26 9:59 ` Hin-Tak Leung
2009-06-26 10:57 ` Andreas Ericsson
2009-06-26 13:44 ` Hin-Tak Leung
2009-06-27 1:17 ` Hin-Tak Leung
2009-06-28 3:08 ` Hin-Tak Leung
2009-07-02 8:16 ` Eric Wong
2009-09-30 22:04 ` Hin-Tak Leung
2009-10-01 7:17 ` Eric Wong
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=3ace41890906251739r45b3eae9oe1b7e32886defc0f@mail.gmail.com \
--to=hintak.leung@gmail.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;
as well as URLs for NNTP newsgroup(s).