From: Junio C Hamano <gitster@pobox•com>
To: Jeff King <peff@peff•net>
Cc: git@vger•kernel.org
Subject: Re: What's cooking in git.git (Mar 2015, #08; Mon, 23)
Date: Tue, 24 Mar 2015 13:02:35 -0700 [thread overview]
Message-ID: <xmqqsicu5fl0.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <xmqqmw338khu.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Mon, 23 Mar 2015 14:35:57 -0700")
Junio C Hamano <gitster@pobox•com> writes:
> * jk/test-chain-lint (2015-03-22) 28 commits
> - t6039: fix broken && chain
> - t9158, t9161: fix broken &&-chain in git-svn tests
> - t9104: fix test for following larger parents
> - t4104: drop hand-rolled error reporting
> - t0005: fix broken &&-chains
> - t7004: fix embedded single-quotes
> - t0050: appease --chain-lint
> - t9001: use test_when_finished
> - t4117: use modern test_* helpers
> - t6034: use modern test_* helpers
> - t1301: use modern test_* helpers
> - t0020: use modern test_* helpers
> - t6030: use modern test_* helpers
> - t9502: fix &&-chain breakage
> - t7201: fix &&-chain breakage
> - t3600: fix &&-chain breakage for setup commands
> - t: avoid using ":" for comments
> - t: wrap complicated expect_code users in a block
> - t: use test_expect_code instead of hand-rolled comparison
> - t: use test_might_fail for diff and grep
> - t: fix &&-chaining issues around setup which might fail
> - t: use test_must_fail instead of hand-rolled blocks
> - t: use verbose instead of hand-rolled errors
> - t: assume test_cmp produces verbose output
> - t: fix trivial &&-chain breakage
> - t: fix moderate &&-chain breakage
> - t: fix severe &&-chain breakage
> - t/test-lib: introduce --chain-lint option
>
> People often forget to chain the commands in their test together
> with &&, leaving a failure from an earlier command in the test go
> unnoticed. The new GIT_TEST_CHAIN_LINT mechanism allows you to
> catch such a mistake more easily.
>
> What I queued here has fix to the issue J6t found in 15/25 squashed
> in, and also has 26/25 and 27/25 follow-up fixes from Michael, plus
> 28/25 follow-up from Torsten. If everybody involved is happy with
> it, we can just proceed with this copy, otherwise I'll let Peff
> reroll. I am happy either way.
I'll merge this to 'next' soonish, unless I hear otherwise. I
double checked 15/25 (i.e. $feature{"forks"}{"default"} = [1];)
so I think we are in good shape.
Thanks.
next prev parent reply other threads:[~2015-03-24 20:02 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 14:18 [PATCH v4] remote: add --fetch and --both options to set-url Peter Wu
2014-12-17 14:32 ` Jeff King
2014-12-17 14:42 ` Peter Wu
2014-12-17 22:31 ` Junio C Hamano
2015-03-23 21:35 ` What's cooking in git.git (Mar 2015, #08; Mon, 23) Junio C Hamano
2015-03-24 20:02 ` Junio C Hamano [this message]
2015-03-24 20:04 ` Jeff King
2015-03-24 20:08 ` Junio C Hamano
2015-03-24 22:21 ` Junio C Hamano
2015-03-26 16:18 ` Jeff King
2015-03-24 22:26 ` Junio C Hamano
2015-03-25 0:37 ` Jakub Narębski
2015-03-25 1:05 ` Junio C Hamano
2015-03-24 23:37 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2014-05-14 18:41 [PATCH/RFC] Gitweb: Convert UTF-8 encoded file names Michael Wagner
2014-05-14 21:57 ` Junio C Hamano
2014-05-14 22:25 ` Jakub Narębski
2014-05-15 5:08 ` Michael Wagner
2014-05-15 9:04 ` Peter Krefting
2014-05-15 17:24 ` Junio C Hamano
2014-05-15 18:48 ` Michael Wagner
2014-05-15 19:28 ` Jakub Narębski
2014-05-15 19:37 ` Jakub Narębski
2014-05-15 19:38 ` Junio C Hamano
2014-05-15 20:45 ` Jakub Narębski
2014-05-16 1:26 ` Junio C Hamano
2014-05-16 7:54 ` Jakub Narębski
2014-05-16 17:05 ` Junio C Hamano
2014-05-27 14:18 ` Jakub Narębski
2014-05-16 18:17 ` Junio C Hamano
2014-05-27 14:22 ` [PATCH] gitweb: Harden UTF-8 handling in generated links Jakub Narębski
2014-06-04 15:41 ` Michael Wagner
2014-06-04 18:47 ` Jakub Narębski
2014-06-04 20:47 ` Michael Wagner
2014-05-15 12:32 ` [PATCH/RFC] Gitweb: Convert UTF-8 encoded file names Jakub Narębski
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=xmqqsicu5fl0.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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