From: Clemens Buchacher <drizzd@aon.at>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: [PATCH 0/5] verify refs early
Date: Mon, 13 Feb 2012 21:17:10 +0100 [thread overview]
Message-ID: <1329164235-29955-1-git-send-email-drizzd@aon.at> (raw)
In-Reply-To: <7vhazobto3.fsf@alter.siamese.dyndns.org>
Hi Junio,
This series centers around "[PATCH 3/5] git push: verify refs early",
which implements your suggestions in reply to my "[PATCH] optionally
deny all pushes". I am not pursuing the deny config option further,
because as you noted, it is of course made redundant by a simple
pre-receive hook.
[PATCH 1/5] git rev-list: fix invalid typecast
I consider this one a fairly important bugfix. Although I was unable to
determine under which circumstances the bug takes effect, rev-list
probably takes a performance hit when it does.
[PATCH 2/5] do not override receive-pack errors
[PATCH 3/5] git push: verify refs early
Note that [PATCH 3/5] makes an extension to the transfer protocol.
[PATCH 4/5] t5541: use configured port number
A mostly unrelated bugfix.
[PATCH 5/5] push/fetch/clone --no-progress suppresses progress
A totally unrelated change. However, this conflicts textually
(lexically?) with [PATCH 3/5], and therefore I am including it here.
Clemens
next prev parent reply other threads:[~2012-02-13 20:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 17:49 [PATCH] optionally deny all pushes Clemens Buchacher
2012-01-21 22:02 ` Junio C Hamano
2012-02-13 20:17 ` Clemens Buchacher [this message]
2012-02-13 20:17 ` [PATCH 1/5] git rev-list: fix invalid typecast Clemens Buchacher
2012-02-13 20:48 ` Junio C Hamano
2012-02-13 20:17 ` [PATCH 2/5] do not override receive-pack errors Clemens Buchacher
2012-02-13 21:41 ` Junio C Hamano
2012-02-14 8:33 ` Clemens Buchacher
2012-02-14 19:06 ` Junio C Hamano
2012-02-13 20:17 ` [PATCH 3/5] git push: verify refs early Clemens Buchacher
2012-02-13 22:16 ` Junio C Hamano
2012-02-14 8:59 ` Clemens Buchacher
2012-02-13 20:17 ` [PATCH 4/5] t5541: use configured port number Clemens Buchacher
2012-02-13 21:23 ` Junio C Hamano
2012-02-13 20:17 ` [PATCH 5/5] push/fetch/clone --no-progress suppresses progress output Clemens Buchacher
2012-02-13 21:13 ` 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=1329164235-29955-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).