Re: Google Summer of Code 2009

From: Stephan Beyer <s-beyer@gmx.net>
Date: Jan 14, 2009, 22:01 UTC
Message-ID: <20090114220112.GC32313@leksak.fem-net>
In-Reply-To: <m3privyn20.fsf@localhost.localdomain>

Hi,

Jakub Narebski wrote:

Show 11 quoted lines

> By the way, do you know what happened with git-sequencer project? 
> 
> If I remember correctly there was agreement on sequences mini-language
> (I think), and there was git-sequencer prototype in shell, using
> git-cherry-pick if I remember correctly, and even git-rebase and
> git-am etc reworked to make use of git-sequencer.  Stephan Beyer wrote
> that he has some preliminary version of builtin git-sequencer (in C),
> and that it makes git-rebase--interactive and like faster than current
> implementation... but builtin sequencer never materialized on git
> mailing list as a patch, if I remember correctly, and of course it was
> not merged into git either.

You remember and conclude correctly.

As Christian pointed out, we are working on it. Development didn't make any real progress for a long time because of different personal reasons. (If you're interested: an important exam at the end of September, some other work besides, wrong priorities in time management, some kind of "burnout" after the exam which made me avoid any kind of productive work for a long time... it went away in between but came back later...)

Now, again, I'm highly motivated to get it merged into pu or next before the end of January. I hope, Christian or Daniel will kick me in the back if this is not going to happen :-) The next days some tiny and some bigger patches will follow. Commits that have been lying around in my repo for a _long_ time.

In this time I try to address the rest of my TODO list which emerged
from a very chaotic sticky note[1] and is, well, just chaotic.
It contains items about...
 - some internal changes (simplifications, code reuse),
 - some changes in the output of sequencer,
 - some better code documentation (one item for a part of sequencer
   itself, one item for its test suite t3350),
 - check some stuff and fix if needed
   (e.g. whether sequencer changes this or that behavior (for
   rebase or am) that I haven't taken care of yet),
 - and the last item is to check/incorporate the git-rebase --root
   patches and/or fix sequencer to work with them (if needed).
   (I haven't taken one look at these patches, so I don't know
   if it's really necessary.)

It's not too much, but every single change can generate a bug and, thus, hassle. :-)

Well, this is the current state of the git-sequencer project. Thanks for the question and the prodding in the other thread (although the problem there was solved much simpler without sequencer.)

Regards,
  Stephan

Footnotes.
 1. I mean those fancy yellow desktop notes provided by tools like
    "knotes" -- now uninstalled from my desktop machine, because
    there are *useful* tools like outliners that _help_ to
    manage ideas, todo lists, etc in a non-chaotic way.

-- 
Stephan Beyer <s-beyer@gmx.net>, PGP 0x6EDDD207FCC5040F