From: Victor Leschuk <vleschuk@gmail.com>
To: git@vger.kernel.org
Cc: vleschuk@accesssoftek.com, normalperson@yhbt.net
Subject: [PATCH 0/2] git-svn: add support for prefixed globs in config
Date: Wed, 16 Dec 2015 16:01:07 +0300 [thread overview]
Message-ID: <1450270869-29822-1-git-send-email-vleschuk@accesssoftek.com> (raw)
There are existing old SVN repos which use patterns in branch (and tag) names
to indicate some information. For example: branches/release_01, branches/release_02, etc,
however non-patterned branches co-exist with them (like branches/dev).
If someone maintains git mirror of such a repo it is reasonable to mirror only
several branches (for example those who match some pattern) and in current situation
it leads to messy and error-prone git config like:
branches = branches/{release_20,release_21,release_22,...
It would be useful to have an opportunity to write
branches = branches/release_*
instead of this.
Thus I suggest to add support for such 'prefixed' globs into git-svn.
Victor Leschuk (2):
Introduce prefixed globs for branches and tags in git-svn.
Add test for git-svn prefixed globs.
Documentation/git-svn.txt | 5 ++
perl/Git/SVN/GlobSpec.pm | 9 ++-
t/t9168-git-svn-prefixed-glob.sh | 136 +++++++++++++++++++++++++++++++++++++++
3 files changed, 145 insertions(+), 5 deletions(-)
create mode 100755 t/t9168-git-svn-prefixed-glob.sh
--
2.7.0.rc0.21.gb793f61
next reply other threads:[~2015-12-16 13:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 13:01 Victor Leschuk [this message]
2015-12-16 13:01 ` [PATCH 1/2] git-svn: support for prefixed globs in config Victor Leschuk
2015-12-16 13:01 ` [PATCH 2/2] git-svn: test for git-svn prefixed globs Victor Leschuk
2015-12-16 21:28 ` Eric Wong
2015-12-16 21:31 ` Victor Leschuk
2015-12-17 0:32 ` 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=1450270869-29822-1-git-send-email-vleschuk@accesssoftek.com \
--to=vleschuk@gmail.com \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
--cc=vleschuk@accesssoftek.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).