Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH 0/9] "git status" that is not "git commit --dry-run"
Date: Sat, 15 Aug 2009 15:39:48 -0700	[thread overview]
Message-ID: <1250375997-10657-1-git-send-email-gitster@pobox.com> (raw)

Here is an update relative to 7637868 (wt-status: collect untracked files
in a separate "collect" phase, 2009-08-10) that has been queued in 'next'.

[PATCH 1/9] and [PATCH 2/9] are the same from last night's fixes.

[PATCH 3/9] through [PATCH 6/9] introduce a new "git status" with
different semantics for 1.7.0 under a tentative name "git stat".  They
will be squashed into one commit in the final round, as 4, 5, and 6 are
fix-ups, but are keft separate for easier review.

    The new "git status" handles paths differently from the traditional
    one.  It used to be the preview of "git commit paths...", IOW,
    "show what would happen if we try to make a partial commit of only
    these paths".  The new "git status" only limits the paths the output
    talks about and is not a preview of anything at all anymore.

    Another semantic change is that its exit status no longer says if
    there is something to be committed in the index.  We used to exit with
    non-zero status if there is nothing to commit.

[PATCH 7/9] introduces a short format output.

The last two patches make the new "git status" official.  They will be
squashed together into one commit in the final round, but are kept
separate for reviewability.

Junio C Hamano (9):
  Documentation/git-commit.txt: describe --dry-run
  git commit --dry-run -v: show diff in color when asked
  git stat: the beginning
  git stat: honor relative paths setting
  git stat: show traditional status headers and trailers as well
  git stat: pathspec limits, unlike traditional "git status"
  git stat -s: short status output
  git status: not "commit --dry-run" anymore
  git-status: adjust tests

 Documentation/git-commit.txt |   13 ++-
 Documentation/git-status.txt |   79 +++++++++++++++++---
 Makefile                     |    1 +
 builtin-commit.c             |  172 +++++++++++++++++++++++++++++++++++++-----
 t/t6040-tracking-info.sh     |    2 +-
 t/t7060-wtstatus.sh          |    8 +-
 t/t7506-status-submodule.sh  |    6 +-
 t/t7508-status.sh            |   12 ++-
 wt-status.c                  |   10 ++-
 wt-status.h                  |    1 +
 10 files changed, 255 insertions(+), 49 deletions(-)

             reply	other threads:[~2009-08-15 22:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-15 22:39 Junio C Hamano [this message]
2009-08-15 22:39 ` [PATCH 1/9] Documentation/git-commit.txt: describe --dry-run Junio C Hamano
2009-08-15 22:39   ` [PATCH 2/9] git commit --dry-run -v: show diff in color when asked Junio C Hamano
2009-08-15 22:39     ` [PATCH 3/9] git stat: the beginning Junio C Hamano
2009-08-15 22:39       ` [PATCH 4/9] git stat: honor relative paths setting Junio C Hamano
2009-08-15 22:39         ` [PATCH 5/9] git stat: show traditional status headers and trailers as well Junio C Hamano
2009-08-15 22:39           ` [PATCH 6/9] git stat: pathspec limits, unlike traditional "git status" Junio C Hamano
2009-08-15 22:39             ` [PATCH 7/9] git stat -s: short status output Junio C Hamano
2009-08-15 22:39               ` [PATCH 8/9] git status: not "commit --dry-run" anymore Junio C Hamano
2009-08-15 22:39                 ` [PATCH 9/9] git-status: adjust tests Junio C Hamano
2009-08-17  8:57                 ` [PATCH 8/9] git status: not "commit --dry-run" anymore 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=1250375997-10657-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