Re: git-svn Rewrites Some Commits, but not All

From: Piotr Krukowiecki <piotr.krukowiecki@gmail.com>
Date: Apr 29, 2014, 22:04 UTC
Message-ID: <CAA01CsoWw2OxuO7e09u18b9-g8c2aavDNWPDE_TvG33-79nwMQ@mail.gmail.com>
In-Reply-To: <CADu-kvcXWXAd2iBt+oQOVt5znxLmU0fmJ-tgOaogyfGjS5R0vA@mail.gmail.com>

On Mon, Apr 28, 2014 at 9:26 PM, Aaron Laws <dartme18@gmail.com> wrote:

Show 6 quoted lines

> The way I understand it, when `git svn dcommit` is run, new commits
> are created (A' is created from A adding SVN information), then the
> current branch is moved to point to A'. Why don't we move any other
> refs that were pointing to A over to A' ? What would be the point of
> continuing to point to A? I'm interested in looking into coding this
> change to git-svn, but I would like to hear some feedback first.

Hi,

I think A' might not always be simply (A + SVN info). I think you can dcommit when you're not up to date. So A' will have a different parent than A (will be automatically rebased on top of current branch tip). Other refs pointing to A might be used as bookmarks, and moving them from A to A' would be a significant change.

-- 
Piotr Krukowiecki