From: "Felipe Contreras" <felipe.contreras@gmail.com>
To: "David Symonds" <dsymonds@gmail.com>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] Implement git-staged, an alias for 'git diff --cached'.
Date: Wed, 29 Oct 2008 21:49:09 +0200 [thread overview]
Message-ID: <94a0d4530810291249x3a1c499xb5dde96de1ac39b3@mail.gmail.com> (raw)
In-Reply-To: <1225237145-95435-1-git-send-email-dsymonds@gmail.com>
On Wed, Oct 29, 2008 at 1:39 AM, David Symonds <dsymonds@gmail.com> wrote:
> Signed-off-by: David Symonds <dsymonds@gmail.com>
> ---
> This isn't a particularly serious patch, but is very relevant to our
> current discussion at GitTogether '08.
I've thought about some commands like:
git stage $file (git add $file)
git unstage $file (git reset $file)
Perhaps
git stage add
git stage rm
And then your proposal would fit with:
git stage diff
Or something like that.
--
Felipe Contreras
prev parent reply other threads:[~2008-10-29 19:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 23:39 [PATCH] Implement git-staged, an alias for 'git diff --cached' 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
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 [this message]
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=94a0d4530810291249x3a1c499xb5dde96de1ac39b3@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=dsymonds@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).