From: Yann Dirson <ydirson@altern.org>
Date: Mon, 11 Dec 2006 18:41:05 GMT
Subject: Re: Collection of stgit issues and wishes
Message-ID: <20061211184105.GC17132@nan92-1-81-57-214-146.fbx.proxad.net>
In-Reply-To: <200612110002.05847.jnareb@gmail.com>

On Mon, Dec 11, 2006 at 12:02:05AM +0100, Jakub Narebski wrote:
> Catalin Marinas wrote:
> > On 10/12/06, Jakub Narebski <jnareb@gmail.com> wrote:
> 
> >> The git commands StGit uses to perform operations automatically record
> >> changes in branches in reflog. What StGit does not provide is the "reason".
> >> You do use git-update-ref?
> > 
> > Yes, only for updating HEAD. The refs in refs/patches/<branch>/ are
> > written directly. I initialy wanted to add patch history support using
> > reflogs and added "git-update-ref -m ..." for the patch commits but I
> > found slow the pushing operation a bit. Do you only want to track the
> > reflogs for HEAD?
> 
> Yes, I want for StGit to provide reasons when updating HEAD.

Apart from the use-case you described in a later mail, this could
provide a path to series-level logging (one of the points in my list);
since the meaningful changes in a series involve changing the HEAD, we
would the have most the needed info that way.

Operations just shuffling the stack (eg. "float -s", or "push XXX;
push --undo") would probably require putting the series file itself