From: Eric Wong <normalperson@yhbt.net>
To: Dmitry Potapov <dpotapov@gmail.com>
Cc: Matt Kern <matt.kern@undue.org>, git@vger.kernel.org
Subject: Re: Git SVN Rebranching Issue
Date: Tue, 4 Nov 2008 16:33:19 -0800 [thread overview]
Message-ID: <20081105003318.GA5666@hand.yhbt.net> (raw)
In-Reply-To: <20081104094224.GC24100@dpotapov.dyndns.org>
Dmitry Potapov <dpotapov@gmail.com> wrote:
> 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 :)
> > 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
next prev parent reply other threads:[~2008-11-05 0:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 14:07 Git SVN Rebranching Issue Matt Kern
2008-11-04 8:41 ` Eric Wong
2008-11-04 9:42 ` Dmitry Potapov
2008-11-04 10:15 ` Sverre Rabbelier
2008-11-04 11:24 ` Matt Kern
2008-11-05 0:33 ` Eric Wong [this message]
2008-11-05 0:40 ` Avery Pennarun
2008-11-06 9:39 ` Eric Wong
2008-11-06 20:48 ` Avery Pennarun
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=20081105003318.GA5666@hand.yhbt.net \
--to=normalperson@yhbt.net \
--cc=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=matt.kern@undue.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