git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH/RFC] git-svn: Allow multiple branch and tag patterns

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Feb 23, 2010, 10:50 UTC
Message-ID
<4B83B303.50408@drmicha.warpmail.net>
In-Reply-To
<c8b3bef91002221429l3b277429l56f4e4cac4fdeb43@mail.gmail.com>
Michael Olson venit, vidit, dixit 22.02.2010 23:29:
Show 16 quoted lines
> 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

Previous: Tim StoakesNext: Michael Olson
Message 3 of 4 in “git-svn: Allow multiple branch and tag patterns”
  1. git-svn: Allow multiple branch and tag patternsMichael Olson, Feb 22, 2010
  2. Tim StoakesFeb 23, 2010
  3. Michael J GruberFeb 23, 2010
  4. Michael OlsonFeb 23, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.