git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Git List <git@vger.kernel.org>,
	Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
	Daniel Barkalow <barkalow@iabervon.org>,
	Christian Couder <chriscool@tuxfamily.org>
Subject: Re: [RFC PATCH v2] revert: Implement --abort processing
Date: Sun, 12 Jun 2011 18:21:57 +0530	[thread overview]
Message-ID: <BANLkTi=gYSJgG-Yu-+-5wPetpb0-AW=X+g@mail.gmail.com> (raw)
In-Reply-To: <20110612122145.GA20495@elie>

Hi again,

Jonathan Nieder writes:
> Would this person expect:
>
>  - that "git diff --cached" would return a pile of changes
>  - that "git reset --keep", "git reset --merge", "git checkout",
>   "git merge", and various other commands would refuse to do much,
>   for fear of clobbering the new "local changes"
>  - that the worktree would be unchanged
>  - etc
>
> Would they be happy about it?  Just put yourself in their shoes.  A
> soft reset is near the most intrusive behavior possible.

Okay, it sounds pretty terrible when you put it like that :p

> And that is a good way to think about the UI for any new facility.  If
> you disregard about how flexible it is in abstract, how easy to
> implement, how elegant-sounding and just think about a person using it
> will find her quality of life improved or worsened, that is (1) a good
> sanity-check on a design and (2) basically the only way to explain it
> to other people.

Frankly, I'm still trying to understand how other people work -- I
don't use the porcelain much, and I dislike anything but the most
minimalistic automation.  I didn't even like the change to cherry-pick
where you can simply "git commit" after resolving a conflict; I still
prefer and use the more explicit "git commit -c" after removing the
CHERRY_PICK_HEAD.  Also, I *always* use rebase with --onto, because I
explicitly want to know how many commits I'm picking, and I often
don't remember if I've rewritten the ref I'm rebasing onto.  While
rebasing, I use reset --hard a lot, because it's a very effective and
well-understood hammer; I then cherry-pick the refs I want from the
reflog.  I don't know how others work; I think I'm completely confused
about UI because I'm trying to mix my personal tastes, historical
conventions, and suggestions from others.
</rant>

Long story short: I'm hopeless at UI design. I'll think about the
sequencer UI from a fresh perspective again, and hopefully post
something sensible soon.

-- Ram

  reply	other threads:[~2011-06-12 12:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-11  6:36 [RFC PATCH v2] revert: Implement --abort processing Ramkumar Ramachandra
2011-06-11 11:22 ` Jonathan Nieder
2011-06-12 12:09   ` Ramkumar Ramachandra
2011-06-12 12:21     ` Jonathan Nieder
2011-06-12 12:51       ` Ramkumar Ramachandra [this message]
2011-06-12 22:12         ` Jonathan Nieder
2011-06-13 14:55           ` Ramkumar Ramachandra
2011-06-13 20:28             ` Jonathan Nieder

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='BANLkTi=gYSJgG-Yu-+-5wPetpb0-AW=X+g@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 \
    --cc=peff@peff.net \
    /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).