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

RE: Problem importing from SVN repository with branches/tags at multiple levels using git-svn

From
JGJim Garrison <jim.garrison@nwea.org>
Date
Jan 22, 2014, 21:11 UTC
Message-ID
<0C723FEB5B4E5642B25B451BA57E273075147566@S1P5DAG3C.EXCHPROD.USA.NET>
In-Reply-To
<52E01601.8090705@sedsystems.ca>
Show 16 quoted lines
> -----Original Message-----
> Behalf Of Robert Hancock
> Sent: Wednesday, January 22, 2014 11:03 AM
> Subject: Re: Problem importing from SVN repository with branches/tags at
> multiple levels using git-svn
> 
> On 01/15/2014 02:10 PM, Robert Hancock wrote:
> > We have an SVN repository that has a structure for tags (likewise for
> > branches) like this:
> >
> > tags/tag1
> > tags/tag2
> > tags/tag3/
> > tags/subdir/tag4
> > tags/subdir/tag5
> >
[snip]
We did this recently and decided there is only one way to do it reliably.
Copy all the tags, within subversion itself, into the structure expected by git, then use git svn following the procedures outlined in the manual.
Copying tags is cheap in subversion, and you can always delete them afterwards if you want.
Previous: Robert Hancock
Message 3 of 3 in “Problem importing from SVN repository with branches/tags at multiple levels using git-svn”
  1. Robert HancockJan 15, 2014
  2. Robert HancockJan 22, 2014
  3. Jim GarrisonJan 22, 2014

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.