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

Re: [PATCH/RFC 0/2] git-svn: Allow certain refs to be ignored

From
EWEric Wong <normalperson@yhbt.net>
Date
Apr 21, 2010, 07:18 UTC
Message-ID
<20100421071759.GA15680@dcvr.yhbt.net>
In-Reply-To
<o2xc8b3bef91004201430m10bbe060q7d8ebd3a1ac4c3bd@mail.gmail.com>
Michael Olson <mwolson@gnu.org> wrote:
Show 13 quoted lines
> This change allows certain refs to be ignored while importing svn
> history.  This is useful for:
> 
>  - Performing overlapping transforms from svn's branch namespace into
>    git's namespace.  The overlapping refs can be ignored.  It might
>    potentially be a better idea in this case to make git-svn assign
>    precedence according to the order in which the branch patterns are
>    specified, perhaps with an option to trigger that behavior (which
>    is out of scope for this patch series).
> 
>  - Avoiding some refs that represent bad svn operations which cause
>    git-svn to take a very long time.  Example: copying one module
>    accidentally into another module's branch namespace.
Hi Michael, these are definitely good things to have.  Thanks!
> A new config directive called "ignore-refs" implements this feature by
> means of a regex of refs to ignore.  I haven't written the necessary
> git-svn documentation updates for it yet.
See Junio's and my other email.
> In addition, I ran across a problem where git-svn would die if a
> parent ref did not exist.  This might possibly have been exposed as a
> result of the first patch.  I threw an eval around the offending code,
> and that seems to work, though some review would be appreciated.

I'm cc-ing Sam for this one. It looks good to me given the first patch would cause more refs to not exist.

-- 
Eric Wong
Previous: Michael Olson
Message 7 of 7 in “git-svn: Allow certain refs to be ignored”
  1. 0/2 git-svn: Allow certain refs to be ignoredMichael Olson, Apr 20, 2010
  2. Junio C HamanoApr 20, 2010
  3. Eric WongApr 21, 2010
  4. Michael OlsonApr 21, 2010
  5. Eric WongApr 21, 2010
  6. Michael OlsonApr 21, 2010
  7. Eric WongApr 21, 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.