From: Hin-Tak Leung <hintak.leung@gmail.com>
To: Andreas Ericsson <ae@op5.se>
Cc: git@vger.kernel.org
Subject: Re: git svn's performance on cloning mono's branches/tags...
Date: Sat, 27 Jun 2009 02:17:25 +0100 [thread overview]
Message-ID: <3ace41890906261817y523c9321xd621fb3130941d91@mail.gmail.com> (raw)
In-Reply-To: <3ace41890906260644t3eddb2d2sb4ddbcb6499801@mail.gmail.com>
Starting afresh with -T/-t/-b is transversing the branches and tags
once, rather that over and over starting from r1.
Here is the starting afresh config:
--------------------------
[svn-remote "svn"]
url = svn://anonsvn.mono-project.com/source
fetch = trunk/mono:refs/remotes/trunk
branches = branches/*/mono/:refs/remotes/*
tags = tags/*/mono/:refs/remotes/tags/*
--------------------------
Here is my attempt at contiuation/changing my mind after getting at trunk only:
--------------------------
[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
-------------------------
the tags, branches, url entries are effectively the same, I think - so
the main difference is using trunk instead of fetch.
Why does it make any difference? The example at the bottom of
git-svn's man page uses the trunk notation. Maybe it should be
changed?
next prev parent reply other threads:[~2009-06-27 1:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 0:39 git svn's performance on cloning mono's branches/tags Hin-Tak Leung
2009-06-26 5:15 ` 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 [this message]
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=3ace41890906261817y523c9321xd621fb3130941d91@mail.gmail.com \
--to=hintak.leung@gmail.com \
--cc=ae@op5.se \
--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).