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

Re: git-svn fetch after tag conversion?

From
Torsten Bögershausen <tboegi@web.de>
Date
Feb 21, 2014, 15:53 UTC
Message-ID
<53077692.4010408@web.de>
In-Reply-To
<CAHd499AnhD9V46uokx6Waj5XwBZCh-N8ms3ihkY99USej+GDOw@mail.gmail.com>
On 2014-02-21 15.42, Robert Dailey wrote:
Show 19 quoted lines
> I'm converting a large SVN repository to a Git repository. I've run
> the first step of `git svn fetch` and now I have all of my branches,
> tags, and trunk. However my tags are still just branches, I have not
> converted them yet.
> 
> As I transition my team over to use Git, I wonder if it is possible to
> convert the tag-branches to real tags and still be able to do `git svn
> fetch` afterwards to continue to pull in changes. My goal is to have
> the git repository as ready as possible so that everyone can swap to
> it at once (and it'll be less downtime before i can push it to
> github). There are some scenarios I worry about:
> 
> - Will git re-fetch the tag-branches if they technically don't exist
> anymore (they would be real tags)?
> - What if a change is made to a tag, what will git-svn do?
> - New tags created, will those just create new tag-branches and I can
> convert them later?
> 
> Thanks in advance.

I stumbled over this as well. As a tag and a branch is "the same" in svn, the best thing we can do is to keep the svn tags as git branches, in the same way svn does.

Would it work if you make a script to tag the svn tags with a different name, like "git_tag_v1.0" or so ?

Otherwise: just set up a test repo and see what happens ;-)
Previous: Robert Dailey
Message 2 of 2 in “git-svn fetch after tag conversion?”
  1. Robert DaileyFeb 21, 2014
  2. Torsten BögershausenFeb 21, 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.