From: Johannes Sixt <j.sixt@viscovery.net>
To: Ping Yin <pkufranky@gmail.com>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH 3/3] buitin-status: Add tests for submodule summary
Date: Wed, 12 Mar 2008 08:38:03 +0100 [thread overview]
Message-ID: <47D7885B.6060500@viscovery.net> (raw)
In-Reply-To: <1205288512-20435-3-git-send-email-pkufranky@gmail.com>
Ping Yin schrieb:
> ---
> t/t7502-status.sh | 76 +++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 76 insertions(+), 0 deletions(-)
Signed-off-by?
Would you please add a test case that uses "git status --amend"? It would
help diagnose failures with regard to "HEAD^" on Windows greatly.
-- Hannes
next prev parent reply other threads:[~2008-03-12 7:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 2:21 [PATCH 1/3] builtin-status: submodule summary support Ping Yin
2008-03-12 2:21 ` [PATCH 2/3] builtin-status: configurable submodule summary size Ping Yin
2008-03-12 2:21 ` [PATCH 3/3] buitin-status: Add tests for submodule summary Ping Yin
2008-03-12 7:38 ` Johannes Sixt [this message]
2008-03-12 7:33 ` [PATCH 1/3] builtin-status: submodule summary support Johannes Sixt
2008-03-13 13:05 ` Ping Yin
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=47D7885B.6060500@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pkufranky@gmail.com \
/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).