From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Git List <git@vger.kernel.org>
Cc: Christian Couder <chriscool@tuxfamily.org>,
Jonathan Nieder <jrnieder@gmail.com>,
Daniel Barkalow <barkalow@iabervon.org>,
Junio C Hamano <gitster@pobox.com>
Subject: [GSoC update] Sequencer: Debating the UI
Date: Mon, 13 Jun 2011 20:53:54 +0530 [thread overview]
Message-ID: <BANLkTinxx5qFuhwsUt3JeXOO7TjBj8wFvw@mail.gmail.com> (raw)
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
next reply other threads:[~2011-06-13 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 15:23 Ramkumar Ramachandra [this message]
2011-06-14 5:31 ` [GSoC update] Sequencer: Debating the UI Jonathan Nieder
2011-06-14 6:00 ` Ramkumar Ramachandra
2011-06-14 11:45 ` Christian Couder
2011-06-20 15:51 ` Ramkumar Ramachandra
2011-06-21 6:21 ` Christian Couder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BANLkTinxx5qFuhwsUt3JeXOO7TjBj8wFvw@mail.gmail.com \
--to=artagnon@gmail.com \
--cc=barkalow@iabervon.org \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).