git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Torsten Bögershausen" <tboegi@web.de>
To: Robert Dailey <rcdailey.lists@gmail.com>, Git <git@vger.kernel.org>
Subject: Re: git-svn fetch after tag conversion?
Date: Fri, 21 Feb 2014 16:53:54 +0100	[thread overview]
Message-ID: <53077692.4010408@web.de> (raw)
In-Reply-To: <CAHd499AnhD9V46uokx6Waj5XwBZCh-N8ms3ihkY99USej+GDOw@mail.gmail.com>

On 2014-02-21 15.42, Robert Dailey wrote:
> 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 ;-)

      reply	other threads:[~2014-02-21 15:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-21 14:42 git-svn fetch after tag conversion? Robert Dailey
2014-02-21 15:53 ` Torsten Bögershausen [this message]

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=53077692.4010408@web.de \
    --to=tboegi@web.de \
    --cc=git@vger.kernel.org \
    --cc=rcdailey.lists@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).