From: "Marcin Wiśnicki" <mwisnicki@gmail.com>
To: git <git@vger.kernel.org>
Subject: Cloning svn project with flat layout (remote wildcard inside path component)
Date: Fri, 17 Sep 2010 23:14:33 +0200 [thread overview]
Message-ID: <AANLkTin7byfdi=K2eN_9Cqx_HQBJatm1qW7zO-te2F-1@mail.gmail.com> (raw)
I'm trying to clone putty project from it's svn repository.
Unfortunately they are using very nonstandard layout where everything
is in a single directory:
/putty = trunk
/putty-branches-* = release branches
/putty-spinoffs = another branch
/putty-0.* = release tags
To get it working I tried following:
[svn-remote "svn"]
url = svn://svn.tartarus.org/sgt
fetch = putty:refs/remotes/trunk
branches = putty-branch-*:refs/remotes/branches/*
branches = putty-{spinoffs}:refs/remotes/branches/putty-*
tags = /putty-[0-9]*:refs/remotes/tags/*
Turns out however, such configuration is invalid since remote
wildcards are supported only in place of whole path component, not as
a part of it.
Obviously, it would be nice if it was working. Consider this a feature
request, if I may make one.
Actually, I have another: support extended regular expressions (with
capture groups) on remote side and back-references on local ref side,
giving the user control over local branch names.
reply other threads:[~2010-09-17 21:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='AANLkTin7byfdi=K2eN_9Cqx_HQBJatm1qW7zO-te2F-1@mail.gmail.com' \
--to=mwisnicki@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).