git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Rast <trast@student.ethz.ch>
To: Eric Raymond <esr@thyrsus.com>
Cc: <git@vger.kernel.org>
Subject: Re: Three issues from a Subversion-to-git migration
Date: Mon, 29 Mar 2010 11:00:12 +0200	[thread overview]
Message-ID: <201003291100.13043.trast@student.ethz.ch> (raw)
In-Reply-To: <20100326120906.F03BB20CD21@snark.thyrsus.com>

Eric Raymond wrote:
> 2. The git-svn migration logic does not handle unmodified SVN tag
> trees well.

The problem here is that git-svn is designed to handle incremental
updates, where it can't know whether some insane SVN user decides to
modify the tag later on.

I've used the following hack to make real tags out of SVN "tags":

git for-each-ref --format="%(refname)" refs/remotes/tags/ |
while read tag; do
    GIT_COMMITTER_DATE="$(git log -1 --pretty=format:"%ad" "$tag")" \
    GIT_COMMITTER_EMAIL="$(git log -1 --pretty=format:"%ce" "$tag")" \
    GIT_COMMITTER_NAME="$(git log -1 --pretty=format:"%cn" "$tag")" \
    git tag -m "$(git log -1 --pretty=format:"%s%n%b" "$tag")" \
    "${tag#refs/remotes/tags/}" "$tag"
done

Disclaimer: it worked last time I used it.  Haven't checked if it got
dusty since.

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

  reply	other threads:[~2010-03-29  9:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-26 12:09 Three issues from a Subversion-to-git migration Eric Raymond
2010-03-29  9:00 ` Thomas Rast [this message]
2010-03-29  9:10   ` Eric Raymond
2010-03-29  9:32     ` Thomas Rast
2010-03-29 10:26       ` Eric Raymond
2010-03-29 15:57     ` Gabriel Filion
2010-03-29 18:01       ` Eric Raymond

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=201003291100.13043.trast@student.ethz.ch \
    --to=trast@student.ethz.ch \
    --cc=esr@thyrsus.com \
    --cc=git@vger.kernel.org \
    /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).