git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephan Beyer <s-beyer@gmx.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Wincent Colaiuta <win@wincent.com>,
	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 16:22:02 +0100	[thread overview]
Message-ID: <20081029152202.GA10029@leksak.fem-net> (raw)
In-Reply-To: <alpine.DEB.1.00.0810291604200.22125@pacific.mpi-cbg.de.mpi-cbg.de>

Hi,

Johannes Schindelin wrote:
> So saying "this is what aliases are for" you ask for _newbies_ to add it 
> for themselves.  We are talking the same newbies who should be helped by 
> that command, and typically do not know that there are Git aliases yet.

I'm not sure if yet more commands really help newbies.

I *see* the problem that talking about the index, the cache and the staging
area can be difficult to newbies.  But then I'd rather vote for "git diff
--staged" (instead of --cached) or "git show --staged" (both make sense
in some way).
Perhaps it is even sufficient to add a help text to "git status", like
this:

 # Changes to be committed:
 #   (use "git reset HEAD <file>..." to unstage)
+#   (use "git diff --cached" to see a diff of staged files)

For me, a "git staged" feels wrong without a "git stage" (alias for
"git add") and "git unstage <file>" (alias for "git reset <file>").
And I think the list of examples can easily be continued.

Regards,
  Stephan

-- 
Stephan Beyer <s-beyer@gmx.net>, PGP 0x6EDDD207FCC5040F

  reply	other threads:[~2008-10-29 15:23 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 [this message]
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
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=20081029152202.GA10029@leksak.fem-net \
    --to=s-beyer@gmx.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=dsymonds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=win@wincent.com \
    --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).