From: Eric Raymond <esr@thyrsus.com>
To: Thomas Rast <trast@student.ethz.ch>
Cc: git@vger.kernel.org
Subject: Re: Three issues from a Subversion-to-git migration
Date: Mon, 29 Mar 2010 05:10:56 -0400 [thread overview]
Message-ID: <20100329091056.GC10538@thyrsus.com> (raw)
In-Reply-To: <201003291100.13043.trast@student.ethz.ch>
Thomas Rast <trast@student.ethz.ch>:
> 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.
Yes. Ideally, I suppose, git-svn (or whatever replaces it) would have
behavior something like this:
1. Turn unmodified tag directories into git tags
2. Turn odified tags into branches.
3. Recognize when a formerly unmodified tag has been modified, remove
the git tag, and turn it into a branch.
> 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.
Wow, that's ugly. But it does look like it ought to work.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
next prev parent reply other threads:[~2010-03-29 9:11 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
2010-03-29 9:10 ` Eric Raymond [this message]
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=20100329091056.GC10538@thyrsus.com \
--to=esr@thyrsus.com \
--cc=git@vger.kernel.org \
--cc=trast@student.ethz.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.