From: Jeff King <peff@peff•net>
To: Sven Strickroth <sven@cs-ware•de>
Cc: git@vger•kernel.org, Junio C Hamano <gitster@pobox•com>
Subject: Re: RFC: git status --amend
Date: Tue, 31 Mar 2015 14:04:14 -0400 [thread overview]
Message-ID: <20150331180414.GB19206@peff.net> (raw)
In-Reply-To: <551AB64F.4030400@cs-ware.de>
On Tue, Mar 31, 2015 at 04:59:27PM +0200, Sven Strickroth wrote:
> for frontends or scripts it would be helpful to be able to use "git
> status" for getting the repository status compared to HEAD~1 instead of
> only HEAD (as provided by "git commit --amend" in the pre-filled commit
> message).
>
> Thus, I'm suggesting to add a "--amend" parameter (or a parameter with a
> better naming) to "git status".
>
> What do you think of this idea?
Once upon a time "git status" really was just "git commit --dry-run".
These days it has diverged a bit. But I think you could get what you
want with:
git commit --dry-run --amend
It even supports alternate styles like --short.
-Peff
next prev parent reply other threads:[~2015-03-31 18:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 14:59 RFC: git status --amend Sven Strickroth
2015-03-31 18:04 ` Jeff King [this message]
2015-03-31 18:35 ` Junio C Hamano
2015-04-01 8:43 ` David Aguilar
2015-04-01 17:16 ` Junio C Hamano
2015-04-03 21:57 ` David Aguilar
2015-04-03 22:05 ` Jeff King
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=20150331180414.GB19206@peff.net \
--to=peff@peff$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=sven@cs-ware$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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