From: Daniel Pocock <daniel@pocock.com.au>
To: Dave Zarzycki <zarzycki@apple.com>
Cc: git@vger.kernel.org
Subject: Re: git-svn: cloning an SVN repo with sub-branches and sub-tags
Date: Fri, 30 Mar 2012 13:16:19 +0100 [thread overview]
Message-ID: <4F75A413.409@pocock.com.au> (raw)
In-Reply-To: <92FA9CF9-7E8E-4DE6-8524-030A0AD33C9E@apple.com>
On 29/03/2012 15:40, Dave Zarzycki wrote:
> You can make this work, but it is very fragile, doesn't scale well, and it only works on recent versions of git. For example, from the LLVM clang project:
...
> branches = cfe/branches/Apple/*:refs/remotes/svn/misc/Apple/*
> branches = cfe/branches/Apple/Necropolis/*:refs/remotes/svn/misc/AppleNecropolis/*
In the first line, (Apple/*), can it accidentally think that Necropolis
is a branch, when it actually appears to be a directory containing branches?
Or does it consider all the lines in the file together?
next prev parent reply other threads:[~2012-03-30 12:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 13:47 git-svn: cloning an SVN repo with sub-branches and sub-tags Daniel Pocock
2012-03-29 14:40 ` Dave Zarzycki
2012-03-30 12:16 ` Daniel Pocock [this message]
2012-03-30 16:20 ` Dave Zarzycki
2012-03-29 15:32 ` Ramkumar Ramachandra
2012-03-30 12:22 ` Daniel Pocock
2012-03-30 12:35 ` Ramkumar Ramachandra
2012-03-29 15:56 ` dag
2012-03-29 16:03 ` Stephen Bash
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=4F75A413.409@pocock.com.au \
--to=daniel@pocock.com.au \
--cc=git@vger.kernel.org \
--cc=zarzycki@apple.com \
/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).