git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Mike <xandrani@gmail.com>
Cc: "Holger Hellmuth" <hellmuth@ira.uka.de>,
	"Massimo Manca" <massimo.manca@micronengineering.it>,
	"Jakub Narebski" <jnareb@gmail.com>,
	"Jonathan Nieder" <jrnieder@gmail.com>,
	git@vger.kernel.org, "Ben Walton" <bwalton@artsci.utoronto.ca>,
	"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>
Subject: Re: Undo last commit?
Date: Thu, 30 Jun 2011 10:20:40 +0530	[thread overview]
Message-ID: <BANLkTim459-Jx2R9GpBdkck7PMAEbamJeA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimZN4swfY13zMjkCbAc9UsGSix02Q@mail.gmail.com>

Hi Mike,

Mike writes:
> I do think that git needs polishing in this way. It was designed by a
> very intelligent programmer... however they can sometimes be the worst
> at user interface design. I think a lot of people are missing out on
> how great git is because of the learning curve, and also the slightly
> odd naming conventions.
>
> "git reset --soft HEAD^" can't be picked up that quickly by a
> beginner, but git uncommit would be obvious! So I have to agree with
> Holger. Good design makes something intuitive. I have used DVD
> recorder / players that are so badly designed that I needed to read
> the instruction manual. Something complicated can be designed to such
> a degree that people rarely have to read a manual, and they can pick
> it up really quickly because it's obvious. If you disagree then you
> might need to learn something about good design because what I say
> isn't opinion it's a fact. Flame away :)

I completely agree with you.  Git's user interface can certainly be
improved -- we have had many many discussions on this topic (like
{1]).  Unfortunately, the way to go about doing it is not to implement
every little suggestion and introduce more inconsistencies;  Git is
very complex, and changing one little thing requires us to think about
how it'll affect everything else.  Yes, it does seem like a daunting
task, but the interface IS improving slowly and steadily.  You can
help by thinking about how a certain new feature will interact with
every component of Git, and participating in UI discussions.

-- Ram

[1]: http://thread.gmane.org/gmane.comp.version-control.git/175061

  reply	other threads:[~2011-06-30  4:51 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 [this message]
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
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=BANLkTim459-Jx2R9GpBdkck7PMAEbamJeA@mail.gmail.com \
    --to=artagnon@gmail.com \
    --cc=bwalton@artsci.utoronto.ca \
    --cc=git@vger.kernel.org \
    --cc=hellmuth@ira.uka.de \
    --cc=jnareb@gmail.com \
    --cc=jrnieder@gmail.com \
    --cc=massimo.manca@micronengineering.it \
    --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 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).