From: Clemens Buchacher <drizzd@aon.at>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: enable push --quiet
Date: Sun, 8 Jan 2012 22:06:18 +0100 [thread overview]
Message-ID: <1326056781-17456-1-git-send-email-drizzd@aon.at> (raw)
Hi Junio,
This is a resend of the push --quiet bugfix "series".
[PATCH 1/3] server_supports(): parse feature list more carefully
[PATCH 2/3] fix push --quiet: add 'quiet' capability to receive-pack
[PATCH 3/3] t5541: avoid TAP test miscounting
I think it was looking good except for the TAP issue that you reported in this
email [1], which Michael "fixes" in PATCH 3/3, but which I could not reproduce
and which was never really understood.
The series is also available as branch cb/push-quiet at
http://github.com/drizzd/git .
Clemens
[1] http://mid.gmane.org/7v62l7crpg.fsf@alter.siamese.dyndns.org
next reply other threads:[~2012-01-08 21:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-08 21:06 Clemens Buchacher [this message]
2012-01-08 21:06 ` [PATCH 1/3] server_supports(): parse feature list more carefully Clemens Buchacher
2012-01-08 21:06 ` [PATCH 2/3] fix push --quiet: add 'quiet' capability to receive-pack Clemens Buchacher
2012-01-08 21:06 ` [PATCH 3/3] t5541: avoid TAP test miscounting Clemens Buchacher
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=1326056781-17456-1-git-send-email-drizzd@aon.at \
--to=drizzd@aon.at \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).