From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH v2 0/3] commit --dry-run
Date: Sat, 8 Aug 2009 00:14:50 -0700 [thread overview]
Message-ID: <1249715693-9715-1-git-send-email-gitster@pobox.com> (raw)
This is a re-roll of the commit in the jc/shortstatus series that has been
kept out of 'pu'.
First, we introduce "git commit --dry-run", which does exactly the same
thing as the current "git status". A longer term goal of this change is
so that we could make "git status" behave completely differently after an
ample warning period.
The second commit introduces a new "git status" under a tentative name
"git stat". In this step, it does not do anything interesting, other than
that it ignores the path parameters.
The third commit adds "-s" option to the new command, to give the "short"
output format.
Probably the next round should insert a commit between the second one and
the third one to take pathspec parameters that are used as path limiters,
but I am too tired for doing that myself tonight.
Junio C Hamano (3):
commit: --dry-run
git stat: the beginning
git stat -s: short status output
Documentation/git-commit.txt | 7 ++-
Makefile | 1 +
builtin-commit.c | 163 ++++++++++++++++++++++++++++++++++++------
builtin.h | 1 +
git.c | 1 +
wt-status.c | 24 ++++---
wt-status.h | 1 +
7 files changed, 165 insertions(+), 33 deletions(-)
next reply other threads:[~2009-08-08 7:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-08 7:14 Junio C Hamano [this message]
2009-08-08 7:14 ` [PATCH v2 1/3] commit: --dry-run Junio C Hamano
2009-08-08 7:14 ` [PATCH v2 2/3] git stat: the beginning Junio C Hamano
2009-08-08 7:14 ` [PATCH v2 3/3] git stat -s: short status output Junio C Hamano
2009-08-08 7:18 ` [PATCH v2 0/3] commit --dry-run Sverre Rabbelier
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=1249715693-9715-1-git-send-email-gitster@pobox.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
/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).