git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Sun, 28 Jun 2009 04:08:01 +0100	[thread overview]
Message-ID: <3ace41890906272008t96bfb04q7218e95055897900@mail.gmail.com> (raw)
In-Reply-To: <3ace41890906261817y523c9321xd621fb3130941d91@mail.gmail.com>

On Sat, Jun 27, 2009 at 2:17 AM, Hin-Tak Leung<hintak.leung@gmail.com> wrote:

> 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?
>

To answer my question - I think the man page should be updated.

Also, while searching 'git svn speed', I found that a git clone of
mono is available:
http://www.mono-project.com/GitSVN
A shame this page is not referenced my other devel resources on mono's
web site at all... also it uses a real user's account to make the
clone (rather than annonymous svn), so to update the git clone by
git-svn, one needs a real dev account - that is not a problem for the
purpose of sending in patches as the occasional dev.

  reply	other threads:[~2009-06-28  3:08 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
2009-06-28  3:08           ` Hin-Tak Leung [this message]
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=3ace41890906272008t96bfb04q7218e95055897900@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).