Re: Git SVN Rebranching Issue

From: Eric Wong <normalperson@yhbt.net>
Date: Nov 5, 2008, 00:33 UTC
Message-ID: <20081105003318.GA5666@hand.yhbt.net>
In-Reply-To: <20081104094224.GC24100@dpotapov.dyndns.org>

Dmitry Potapov <dpotapov@gmail.com> wrote:

Show 8 quoted lines

> On Tue, Nov 04, 2008 at 12:41:11AM -0800, Eric Wong wrote:
> > 
> > Short answer: you can use grafts to remove parents.
> 
> Using grafts requires some cautious, especially when it is used to make
> some commits unreachable, because git gc can remove unreachable commits.
> Also, a repository with grafts cannot be cloned.  So using grafts looks
> like more as workaround rather a real solution.

I don't think extra history is harmful at all, so the grafts could even be temporary. AFAIK, the extra history is only an aesthetic issue in visualizers (and I actually like to see it myself).

Besides, git svn is just a workaround until the SVN repository is replaced entirely by git :)

Show 6 quoted lines

> > It was actually an intentional design decision on my part preserve
> > parents based on branch name.  We would eventually otherwise lose
> > history of the now-deleted branches, as reflogs can expire.
> 
> Would it not be better to save the old branch using "@SVN-NUMBER" as
> suffix? Thus, those do not need the old branch can easily delete it.

That would require renaming _existing_ branches to their "@SVN-NUMBER" name; which would break mechanisms for tracking branches based on refname.

-- 
Eric Wong