From: Junio C Hamano <gitster@pobox.com>
Date: Wed, 02 Jul 2008 01:20:15 GMT
Subject: Re: [RFC/PATCH 2/4] Add git-sequencer prototype documentation
Message-ID: <7v4p79hyk0.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <200807020239.41613.jnareb@gmail.com>

Jakub Narebski <jnareb@gmail.com> writes:

>> No. It is "git-update-ref <ref> HEAD".
>
> So what do you envision would this be used for?

A simple answer and a more elaborate one.

 * It is the final step of "git rebase" which detaches HEAD while it
   operates these days.

 * You can drive sequencer backend from a front-end that rewrite history
   while rewriting tags, like filter-branch does.

>>> What is important is: does it update reflog (correctly)?

That is not very important question, as reflog updates would happen as
long as you use update-ref automatically.

Much more important question you did not ask is how it would interact with
"sequencer --abort".  Ideally it should rewind the ref update (and without
relying on the user having reflog on that ref).

I however personally feel that this "ref" thing is being a bit too
ambitious.