From: Eric Raymond <esr@thyrsus•com>
To: Gabriel Filion <lelutin@gmail•com>
Cc: Thomas Rast <trast@student•ethz.ch>, git@vger•kernel.org
Subject: Re: Three issues from a Subversion-to-git migration
Date: Mon, 29 Mar 2010 14:01:58 -0400 [thread overview]
Message-ID: <20100329180158.GB12922@thyrsus.com> (raw)
In-Reply-To: <4BB0CDEC.8000708@gmail.com>
Gabriel Filion <lelutin@gmail•com>:
> > 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.
>
> The 3rd point seems a bit weird to me.. users don't expect tags to
> disappear magically. Especially if it's done during a fetch while working.
A reasonable objection.
> Here's how I would change the scenario:
>
> 1. For each creation of a sub-directory in SVN's tag directory, create a
> git tag on the revision that was referenced by the directory copy in SVN.
> 2. If (and only if) there are later modifications in the tag directory,
> create a branch starting from that tag.
>
> This way, the tag would be there but a branch would hold modifications
> based on code at this point, if there is any.
That would work for me.
> The problem with my scenario, though is that it doesn't take care of tag
> creation + modification in the same commit (yuukkkk, but it's possible
> that it exists somewhere). If it could be possible to verify if
> modifications were made during the tag creation, then we could make the
> case hit both points.
Doesn't seem like that should be difficult.
> The other big "thing" is that it expects a certain correct separation
> into different directories (e.g. trunk/ tags/ branches/ ), which SVN
> doesn't enforce.
Are you suggesting that branch directory copies should be handled with
the same rule? I think I could live with that.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
prev parent reply other threads:[~2010-03-29 18:02 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
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 [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=20100329180158.GB12922@thyrsus.com \
--to=esr@thyrsus$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=lelutin@gmail$(echo .)com \
--cc=trast@student$(echo .)ethz.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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