From: Michael J Gruber <git@drmicha.warpmail.net>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/2] Add a few more status tests
Date: Tue, 8 Dec 2009 11:12:00 +0100 [thread overview]
Message-ID: <cover.1260266027.git.git@drmicha.warpmail.net> (raw)
Here are a few more tests for git status. The first one makes sure that
--porcelain uses paths based on the root, it makes sense on top of
14ed05d (t7508-status.sh: Add tests for status -s, 2009-11-27) or later.
The second one checks long, short and porcelain with color. It makes
sense on top of 3fe2a89 (status -s: obey color.status, 2009-12-05),
although one test will fail without the later 8661768 (status: reduce
duplicated setup code, 2009-12-07) and predecessor.
Remarks:
- There's not a single merge related status test so far.
- There's no test with -z because I don't know what it's suppoded to
(besides the obvious thing): should it turn off color automatically
but not relativePaths? Or should it switch to --porcelain -z?
Depending on the answer to the latter I have to do one more fixup to
wt-status.c (and write another test).
Thanks:
to J6t for pointing me to decrypt_color()
Michael J Gruber (2):
t7508-status: status --porcelain ignores relative paths setting
t7508-status: test all modes with color
t/t7508-status.sh | 137 +++++++++++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 137 insertions(+), 0 deletions(-)
next reply other threads:[~2009-12-08 10:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 10:12 Michael J Gruber [this message]
2009-12-08 10:12 ` [PATCH 1/2] t7508-status: status --porcelain ignores relative paths setting Michael J Gruber
2009-12-08 10:12 ` [PATCH 2/2] t7508-status: test all modes with color Michael J Gruber
2009-12-08 11:10 ` Jakub Narebski
2009-12-08 16:06 ` Michael J Gruber
2009-12-09 5:32 ` Junio C Hamano
2009-12-09 5:44 ` Junio C Hamano
2009-12-09 9:18 ` Michael J Gruber
2009-12-09 21:59 ` Junio C Hamano
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=cover.1260266027.git.git@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.