From: Jakub Suder <jakub.suder@gmail.com>
Date: Thu, 11 Feb 2010 13:26:23 GMT
Subject: Re: git-subtree.sh - regression introduced by da949cc55
Message-ID: <508e1531002110526u623bffbdi119d009a7af460b8@mail.gmail.com>
In-Reply-To: <20100211130837.GA29916@lonquimay.wrk.lsn.camptocamp.com>

On Thu, Feb 11, 2010 at 14:08, Marc Fournier
<marc.fournier@camptocamp.com> wrote:
> Jakub, I'm not sure I understand what this patch is supposed to fix. Could
> you provide an example ? Or a test case ?

Hi,

there is a test case for the change you're talking about - it's near
the end of test.sh, between "check if split can find proper base
without --onto" and "check_equal ..." (it was added a few commits
later). The problem was that without this commit, in some cases if I
called subtree split for an external project which was earlier added
with git subtree (in order to backport some changes to the original
project) it didn't create the new commits on top of the existing ones
like it should (just look at the test case).

I'll take a closer look at this in the evening...

Jakub Suder