From: Chris Webb <chris@arachsys.com>
To: Johannes Sixt <j6t@kdbg.org>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Sverre Rabbelier <srabbelier@gmail.com>
Subject: Re: Tests with broken && chains in pu
Date: Sun, 4 Apr 2010 21:45:09 +0100 [thread overview]
Message-ID: <20100404204509.GA31315@arachsys.com> (raw)
In-Reply-To: <201004042208.58939.j6t@kdbg.org>
Johannes Sixt <j6t@kdbg.org> writes:
> two commits in pu currently add tests with broken && chains:
> abbfd017 in cw/ws-indent-with-tab:
Thanks for spotting this mistake Johannes. Should I resubmit a corrected
version of the patch, Junio, or do you prefer to squash fixups directly into
the pu branch?
Best wishes,
Chris.
next prev parent reply other threads:[~2010-04-04 20:47 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
2010-04-04 20:45 ` Chris Webb [this message]
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=20100404204509.GA31315@arachsys.com \
--to=chris@arachsys.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--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).