Re: Announcing git-reparent

From: Piotr Krukowiecki <piotr.krukowiecki@gmail.com>
Date: Jan 14, 2013, 08:03 UTC
Message-ID: <CAA01Csoh24ppo37fzptzZKvFrzGQyhz-0eDTQsP8tZiTRQ2YwA@mail.gmail.com>
In-Reply-To: <20130114071608.GL3125@elie.Belkin>

Hello,

On Mon, Jan 14, 2013 at 8:16 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:

Show 11 quoted lines

> Hi Mark,
>
> Mark Lodato wrote:
>
>> Create a new commit object that has the same tree and commit message as HEAD
>> but with a different set of parents.  If ``--no-reset`` is given, the full
>> object id of this commit is printed and the program exits
>
> I've been wishing for something like this for a long time.  I used to
> fake it using "cat-file commit", sed, and "hash-object -w" when
> stitching together poorly imported history using "git replace".

Just wondering, is the result different than something like

git checkout commit_to_reparent cp -r * ../snapshot/ git reset --hard new_parent rm -r * cp -r ../snapshot/* . git add -A

(assumes 1 parent, does not cope with .dot files, and has probably other small problems)

-- Piotr Krukowiecki