From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>
Subject: [PATCH 0/6] "git commit --dry-run" updates
Date: Sat, 15 Aug 2009 03:06:37 -0700 [thread overview]
Message-ID: <1250330803-22171-1-git-send-email-gitster@pobox.com> (raw)
The first patch describes --dry-run option, and stops mentioning the
equivalence to "git status" in the documentation for "git commit".
The second one fixes "git commit --dry-run -v", which did not show the
diff text in color when asked with the configuration.
The third and the fourth ones tentatively introduce "git stat". The
former is an incomplete implementation that ignores the pathspec, and the
latter adds pathspec limiting to it. In the final form before it goes to
'next', these two should probably be squashed.
The fifth one introduces "git stat -s" (short output format) that is
designed to be machine readable, especially with -z (NUL termination).
The sixth one renames "git stat" to take over the traditional "git status"
and obviously is a 1.7.0 material.
The tests still have breakages that future updates to the sixth patch need
to fix. t4030 still assumes "git status" is "git commit --dry-run" and
expects it to take "-v" to produce diffs, for example.
next reply other threads:[~2009-08-15 10:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-15 10:06 Junio C Hamano [this message]
2009-08-15 10:06 ` [PATCH 1/6] Documentation/git-commit.txt: describe --dry-run Junio C Hamano
2009-08-15 10:06 ` [PATCH 2/6] git commit --dry-run -v: show diff in color when asked Junio C Hamano
2009-08-15 10:06 ` [PATCH 3/6] git stat: the beginning Junio C Hamano
2009-08-15 10:06 ` [PATCH 4/6] git stat: pathspec limits, unlike traditional "git status" Junio C Hamano
2009-08-15 10:06 ` [PATCH 5/6] git stat -s: short status output Junio C Hamano
2009-08-15 10:06 ` [PATCH 6/6] git status: not "commit --dry-run" anymore Junio C Hamano
2009-08-17 10:01 ` [PATCH 0/6] "git commit --dry-run" updates Thomas Rast
2009-08-17 15:57 ` Junio C Hamano
2009-08-17 19:16 ` Thomas Rast
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=1250330803-22171-1-git-send-email-gitster@pobox.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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