All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Michael Olson <mwolson@gnu.org>
Cc: git@vger.kernel.org, Eric Wong <normalperson@yhbt.net>
Subject: Re: [PATCH/RFC] git-svn: Allow multiple branch and tag patterns
Date: Tue, 23 Feb 2010 11:50:43 +0100	[thread overview]
Message-ID: <4B83B303.50408@drmicha.warpmail.net> (raw)
In-Reply-To: <c8b3bef91002221429l3b277429l56f4e4cac4fdeb43@mail.gmail.com>

Michael Olson venit, vidit, dixit 22.02.2010 23:29:
> This change allows multiple branch and tag patterns to be specified in
> .git/config for git-svn projects.  This is useful for fetching several
> different parts out of the namespace of an svn repository.
> Additionally, a new repeatable directive called "skip" has been added
> to specify a specific tag or branch to ignore.
> 
> Signed-off-by: Michael W. Olson <mwolson@gnu.org>
> ---
> I've been using this patch regularly for over a year on a very large
> svn repository.
> 
> This patch is known to work on git 1.6.3.3 specifically.  Once I get a
> few responses about whether or not it is useful, I'll rebase it
> against the git.git master branch.  Some further documentation
> (perhaps just a relevant example or two) would also need to be added
> to the git-svn manpage.

I'm sorry, but we have this (multiple branch/tag lines) since 1.6.4, see

6224406 (git svn: Support multiple branch and tag paths in the svn
repository., 2009-06-23)

The skip directive may be obsoleted by

0757620 (git-svn: allow subset of branches/tags to be specified in glob
spec, 2010-01-23)

Cheers,
Michael

  parent reply	other threads:[~2010-02-23 10:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-22 22:29 [PATCH/RFC] git-svn: Allow multiple branch and tag patterns Michael Olson
2010-02-23  2:50 ` Tim Stoakes
2010-02-23 10:50 ` Michael J Gruber [this message]
2010-02-23 14:41   ` Michael Olson

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=4B83B303.50408@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=mwolson@gnu.org \
    --cc=normalperson@yhbt.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.