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

You have a great attitude to design (especially that of software).

I love it when people take feedback as a positive thing, and not as a
criticism! :)

2011/6/30 Jonathan Nieder <jrnieder@gmail.com>:
> Ramkumar Ramachandra wrote:
>> 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.
> [...]
>> Git is
>> very complex, and changing one little thing requires us to think about
>> how it'll affect everything else.
>
> Oh, dear.  No, I don't think these things are true at all (or at least I
> hope we act so as to make them not true).  In its history, just like Jakub
> likes to remind us now and then, git _evolved_.  To make it better, it
> should be sufficient to do three things:
>
>  1. When there is a small, obvious change that can make something
>    better, do it.
>
>  2. When there is a small, obvious change that can make git simpler
>    and more flexible (so other changes can become small and obvious),
>    do it.
>
>  3. When there is a big, possibly advantageous change, try it out
>    locally (e.g., on a branch).  If it turns out to work well, use it.
>
> While it is always nice to see people thinking carefully, none of the
> above necessarily requires thinking about all of git at once.  In
> particular, (2) suggests that any feature leading a well informed
> person to say "Git is very complex" is a bug.
>

  reply	other threads:[~2011-06-30 19:48 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 [this message]
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='BANLkTinLMez=nv4fTcFWtqRb01231sMT1g@mail.gmail.com' \
    --to=xandrani@gmail.com \
    --cc=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 \
    /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).