From: Scott Parish <sRp@srparish.net>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] "git help" and "git help -a" shouldn't exit(1) unless they error
Date: Sun, 21 Oct 2007 23:19:19 -0700 [thread overview]
Message-ID: <20071022061918.GM16291@srparish.net> (raw)
In-Reply-To: <20071022054741.GP14735@spearce.org>
On Mon, Oct 22, 2007 at 01:47:41AM -0400, Shawn O. Pearce wrote:
> The issue here is t0000-basic.sh runs "../git" and tests that the
> exit status is 1. If it isn't (the patch above makes it 0) we just
> abort the test suite entirely.
Shoot, i hadn't realized i had effected the "git" case. I'll
look into this further.
By the way, should i expect all the tests to pass from the unmodified
public HEAD? (they don't for me)
sRp
--
Scott Parish
http://srparish.net/
next prev parent reply other threads:[~2007-10-22 6:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-21 21:47 [PATCH] "git help" and "git help -a" shouldn't exit(1) unless they error Scott R Parish
2007-10-22 5:47 ` Shawn O. Pearce
2007-10-22 6:19 ` Scott Parish [this message]
2007-10-22 6:37 ` Shawn O. Pearce
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=20071022061918.GM16291@srparish.net \
--to=srp@srparish.net \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).