git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wincent Colaiuta <win@wincent.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: David Symonds <dsymonds@gmail.com>,
	git@vger.kernel.org, gitster@pobox.com, Jeff King <peff@peff.net>
Subject: Re: [PATCH] Implement git-staged, an alias for 'git diff --cached'.
Date: Wed, 29 Oct 2008 20:44:58 +0100	[thread overview]
Message-ID: <C03E504F-50E8-4887-80CE-2C6B2F824B9E@wincent.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0810292022480.22125@pacific.mpi-cbg.de.mpi-cbg.de>

El 29/10/2008, a las 20:23, Johannes Schindelin escribió:

> Hi,
>
> On Wed, 29 Oct 2008, Wincent Colaiuta wrote:
>
>> El 29/10/2008, a las 18:03, Johannes Schindelin escribió:
>>
>>> On Wed, 29 Oct 2008, Wincent Colaiuta wrote:
>>>
>>>> Git already has too many commands. Adding more is not going to  
>>>> clear
>>>> up newbie confusion, and will only waste time because people will
>>>> complain about it and ask why there is this kind of duplication.
>>>
>>> I completely disagree.  If the existing set of commands causes
>>> confusion, we need to deprecate those parts and add new commands.
>>> Even if we have a ton of commands already.
>>
>> The confusion isn't at the command level; it's at the switch/option
>> level. The solution isn't to add a new command.
>
> Seems that at leat one guy who does Git training disagrees with you,  
> _in
> addition_ to me.

That's what I call a "zero value" addition to the thread, seeing as  
anyone reading the thread _already_ knows the opinions of the  
participants who've posted.

Adding a separate command to an already overwhelming command set in  
order to address confusion about options to "git diff" is a case of  
"duct-tape UI design".

Wincent

  reply	other threads:[~2008-10-29 19:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-28 23:39 David Symonds
2008-10-28 23:46 ` Jeff King
2008-10-28 23:59 ` David Symonds
2008-10-29  0:39   ` Jeff King
2008-10-29  0:44     ` David Symonds
2008-10-29  1:02       ` Johannes Schindelin
2008-10-29  0:58         ` Jeff King
2008-10-29 10:59       ` Wincent Colaiuta
2008-10-29 15:08         ` Johannes Schindelin
2008-10-29 15:22           ` Stephan Beyer
2008-10-29 15:48             ` Johannes Schindelin
2008-10-29 16:16           ` Wincent Colaiuta
2008-10-29 17:03             ` Johannes Schindelin
2008-10-29 17:13               ` Pascal Obry
2008-10-29 17:42               ` Wincent Colaiuta
2008-10-29 18:30                 ` Teemu Likonen
2008-10-29 20:24                   ` David Kågedal
2008-10-29 19:23                 ` Johannes Schindelin
2008-10-29 19:44                   ` Wincent Colaiuta [this message]
2008-10-29  1:01     ` Stephan Beyer
2008-10-29  1:05       ` Jeff King
2008-10-29 14:33         ` Brandon Casey
2008-10-29 15:19           ` Jeff King
2008-10-29 14:58 ` Pascal Obry
2008-10-29 19:49 ` Felipe Contreras

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=C03E504F-50E8-4887-80CE-2C6B2F824B9E@wincent.com \
    --to=win@wincent.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=dsymonds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --subject='Re: [PATCH] Implement git-staged, an alias for '\''git diff --cached'\''.' \
    /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

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).