All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Mike <xandrani@gmail.com>
Cc: "Neal Kreitzinger" <nkreitzinger@gmail.com>,
	"Holger Hellmuth" <hellmuth@ira.uka.de>,
	"Massimo Manca" <massimo.manca@micronengineering.it>,
	"Jonathan Nieder" <jrnieder@gmail.com>,
	"Ben Walton" <bwalton@artsci.utoronto.ca>,
	"Ramkumar Ramachandra" <artagnon@gmail.com>,
	"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
	git@vger.kernel.org
Subject: Re: Undo last commit?
Date: Sat, 11 Feb 2012 23:07:09 +0100	[thread overview]
Message-ID: <201202112307.10528.jnareb@gmail.com> (raw)
In-Reply-To: <CAHK-92oMc62O0S8Bxt6+uxobE+kg5wOeRDoOsHWvvenXaXmZGQ@mail.gmail.com>

Please do not top-post, and do not remove git mailing list from Cc.
Sorry for double posting; forgot to re-add git@vger.kernel.org

On Sat, 11 Feb 2012, Mike ??? wrote:
> 2012/2/11 Neal Kreitzinger <nkreitzinger@gmail.com>
> > On 6/28/2011 8:57 AM, Holger Hellmuth wrote:
> > >
> > > It would be a nice companion to the not-yet-realized "git unadd" ;-)
> >
> > or perhaps "git unstage"...
>
> If lot's of people have the same problem then it IS a design flaw. If
> something is designed well and genuinely intuitive then they just work.
> Think iPhone, iPod, some DVD players and other well designed user
> interfaces. The same goes for command line tools... the options should have
> names that don't have any ambiguity.
> 
Many of problems with git user interface have their source from the fact
that git, including its interface, was evolved rather than created using
big-design-upfront workflow.  And it _had_ to be evolved, as there was not
much of prior art (well, not good prior art) in the area of DVCS.

Besides, as they say:

  The only "intuitive" interface is the nipple. After that it's all learned.

                                                             -- Bruce Ediger

> Techie guys almost always blame the users, this is a very bad attitude. For
> example I've met so many techies that THINK they can design websites...
> err... they can't. They CAN program sure, but they CAN'T design the user
> experience properly as that is not their expertise. Just as we wouldn't
> expect a graphic designer or user interface specialist to do the coding.
> 
There is also problem in that you need to know git well to _code_ interface;
and when you know git well you don't notice no longer the problems that you
had as a newbie.

On the other hand new git users sometimes have problems distinguishing
between accidental complexity of bad UI design, and essential complexity
of a powerfull and flexible tool.

[...]

So, Mike, will you bitch or will you try to help?

-- 
Jakub Narebski
Poland

  parent reply	other threads:[~2012-02-11 22:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-18 13:15 Undo last commit? Mike
2011-06-18 13:43 ` Ben Walton
2011-06-18 13:48 ` Ramkumar Ramachandra
2011-06-18 13:54 ` Jakub Narebski
2011-06-19  0:37   ` Jonathan Nieder
2011-06-19 10:37     ` Jakub Narebski
2011-06-20 12:08       ` Massimo Manca
2011-06-28 13:57         ` Holger Hellmuth
2011-06-28 14:31           ` Mike
2011-06-30  4:50             ` Ramkumar Ramachandra
2011-06-30 18:38               ` Jonathan Nieder
2011-06-30 19:48                 ` Mike
2011-06-30 17:29             ` Junio C Hamano
2012-02-11 18:19           ` Neal Kreitzinger
     [not found]             ` <CAHK-92oMc62O0S8Bxt6+uxobE+kg5wOeRDoOsHWvvenXaXmZGQ@mail.gmail.com>
2012-02-11 22:07               ` Jakub Narebski [this message]
2012-02-11 22:29                 ` 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=201202112307.10528.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=artagnon@gmail.com \
    --cc=bwalton@artsci.utoronto.ca \
    --cc=git@vger.kernel.org \
    --cc=hellmuth@ira.uka.de \
    --cc=jrnieder@gmail.com \
    --cc=massimo.manca@micronengineering.it \
    --cc=nkreitzinger@gmail.com \
    --cc=pclouds@gmail.com \
    --cc=xandrani@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.