From: Johannes Sixt <j6t@kdbg.org>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Chris Webb <chris@arachsys.com>
Subject: Re: Tests with broken && chains in pu
Date: Sun, 4 Apr 2010 22:41:17 +0200 [thread overview]
Message-ID: <201004042241.17655.j6t@kdbg.org> (raw)
In-Reply-To: <v2yfabb9a1e1004041315x999376f6m7dd689b529ce33d8@mail.gmail.com>
On Sonntag, 4. April 2010, Sverre Rabbelier wrote:
> Thanks for noticing, may I ask how you noticed? Do you have a script
> or was it manual review?
It was manual review. I reviewed the patches in pu because I noticed a broken
&& chain in a recently submitted patch, but I didn't remember which one it
was. So I took the time to look at all new test cases in pu after Junio's
recent What's in git message.
-- Hannes
next prev parent reply other threads:[~2010-04-04 20:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-04 20:08 Tests with broken && chains in pu Johannes Sixt
2010-04-04 20:15 ` Sverre Rabbelier
2010-04-04 20:41 ` Johannes Sixt [this message]
2010-04-04 20:45 ` Chris Webb
2010-04-04 21:28 ` 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=201004042241.17655.j6t@kdbg.org \
--to=j6t@kdbg.org \
--cc=chris@arachsys.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=srabbelier@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).