[GSoC update] Sequencer: Debating the UI

[GSoC update] Sequencer: Debating the UI

[Ramkumar Ramachandra]

Hi,

Frankly, I'm a little worried about not having sent out anything
significant since last week -- I've just been bouncing back and fourth
trying to decide how to structure the UI. After trying out various
forms of --abort, I've decided to drop all UI and just write
"infrastructure code" for the moment, and letting end users decide the
shortcuts for themselves.  Among the various suggestions, I especially
liked Jonathan's --edit solution where the user gets a copy of the
entire instruction sheet (not just commands left to execute) to edit
as she pleases [1].  I've just started working on this.  I might like
to send a quick series based on my earlier series for inclusion, but I
can't figure out a good subset: Everything until "revert: Catch
incompatible command-line options early" might be a candidate for a
simple revert-cleanup series, but most of the motivation for the
cleanup comes from the sequencer needing it.

Thanks for reading.

-- Ram

[1]: http://mid.gmane.org/20110611112213.GA25268@elie

Re: [GSoC update] Sequencer: Debating the UI

[Jonathan Nieder]

Ramkumar Ramachandra wrote:

> I might like
> to send a quick series based on my earlier series for inclusion, but I
> can't figure out a good subset:

I would love to use a working "cherry-pick --continue". :)  I would
use it like this:

	$ : grumble, grumble, source package format that requires a
	$ : tarball followed by a linear sequence of patches
	$ git checkout -b release+patches v1.0
	$ git cherry-pick --no-merges -x -s HEAD..origin/master
	... ticks away for a while, then presents a conflict
	$ git diff; fix fix fix; git add -u; make test; git commit -v
	$ git cherry-pick --continue
	...

	$ git diff origin/master; # matches up?  good.
	$ git format-patch -k --patience -o patches v1.0..HEAD

Speaking of which, do you have a git tree that testers should use /
send patches against?  E.g., is the "sequencer" branch at
git://github.com/artagnon/git.git the one to play with?

Thanks; exciting times.

Regards,
Jonathan

Re: [GSoC update] Sequencer: Debating the UI

[Ramkumar Ramachandra]

Hi,

Jonathan Nieder writes:
> I would love to use a working "cherry-pick --continue". :)  I would
> use it like this:

Great.  I hope to have a mockup of this ready in a couple of days or so.

> Speaking of which, do you have a git tree that testers should use /
> send patches against?  E.g., is the "sequencer" branch at
> git://github.com/artagnon/git.git the one to play with?

Yes.

-- Ram

Re: [GSoC update] Sequencer: Debating the UI

[Christian Couder]

Hi,

On Tue, Jun 14, 2011 at 8:00 AM, Ramkumar Ramachandra
<artagnon@gmail.com> wrote:
> Hi,
>
> Jonathan Nieder writes:
>> I would love to use a working "cherry-pick --continue". :)  I would
>> use it like this:
>
> Great.  I hope to have a mockup of this ready in a couple of days or so.

Yeah, you can work on "cherry-pick --skip" too.
If you have --continue and --skip working, maybe it will be worth merging as is.

Thanks,
Christian.

Re: [GSoC update] Sequencer: Debating the UI

[Ramkumar Ramachandra]

Hi,

Ramkumar Ramachandra wrote:
> Jonathan Nieder writes:
>> I would love to use a working "cherry-pick --continue". :)  I would
>> use it like this:
>
> Great.  I hope to have a mockup of this ready in a couple of days or so.

Gah, it took much longer than expected.  My latest work is in the
'sequencer-continue' branch on my GitHub.  It's almost there; will
send to list after polishing it for a few hours in the morning.

Thanks.

-- Ram

Re: [GSoC update] Sequencer: Debating the UI

[Christian Couder]

Hi Ram,

On Monday 20 June 2011 17:51:23 Ramkumar Ramachandra wrote:
> Hi,
> 
> Ramkumar Ramachandra wrote:
> > Jonathan Nieder writes:
> >> I would love to use a working "cherry-pick --continue". :)  I would
> > 
> >> use it like this:
> > Great.  I hope to have a mockup of this ready in a couple of days or so.
> 
> Gah, it took much longer than expected.  My latest work is in the
> 'sequencer-continue' branch on my GitHub.  It's almost there; will
> send to list after polishing it for a few hours in the morning.

Great! Please post a small status update too.

Thanks,
Christian.