From: Junio C Hamano <gitster@pobox.com>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: [PATCH] {fetch,receive}-pack: skip sha-1 integrity test on objects from new pack
Date: Thu, 15 Mar 2012 20:42:02 -0700 [thread overview]
Message-ID: <7v4ntpi54l.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CACsJy8D5UNd5b=Dpt75Qrc96u6wRLffB7eGSsKqM3qQ37p4cOw@mail.gmail.com> (Nguyen Thai Ngoc Duy's message of "Fri, 16 Mar 2012 09:28:19 +0700")
Nguyen Thai Ngoc Duy <pclouds@gmail.com> writes:
> What about push/receive-pack? I think the same thing happens there.
As the patch goes to check_everything_connected(), it is automatically
covered, no?
next prev parent reply other threads:[~2012-03-16 3:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 15:39 [PATCH] Perform cheaper connectivity check when pack is used as medium Nguyễn Thái Ngọc Duy
2012-02-27 18:14 ` Junio C Hamano
2012-02-28 13:18 ` [PATCH v2] " Nguyễn Thái Ngọc Duy
2012-02-28 15:40 ` Johannes Sixt
2012-02-28 15:47 ` Andreas Ericsson
2012-02-29 1:41 ` Nguyen Thai Ngoc Duy
2012-03-02 6:10 ` Junio C Hamano
2012-03-02 14:05 ` Nguyen Thai Ngoc Duy
2012-03-02 17:31 ` Junio C Hamano
2012-03-03 3:05 ` Nguyen Thai Ngoc Duy
2012-03-03 6:59 ` Junio C Hamano
2012-03-03 10:09 ` Nguyen Thai Ngoc Duy
2012-03-06 11:20 ` Nguyen Thai Ngoc Duy
2012-03-06 15:56 ` Junio C Hamano
2012-03-14 14:40 ` [PATCH] {fetch,receive}-pack: skip sha-1 integrity test on objects from new pack Nguyễn Thái Ngọc Duy
2012-03-14 19:05 ` Junio C Hamano
2012-03-15 21:09 ` Junio C Hamano
2012-03-15 21:57 ` Junio C Hamano
2012-03-16 2:28 ` Nguyen Thai Ngoc Duy
2012-03-16 3:42 ` Junio C Hamano [this message]
2012-03-16 3:42 ` Nguyen Thai Ngoc Duy
2012-03-16 2:24 ` Nguyen Thai Ngoc Duy
2012-03-16 3:46 ` 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=7v4ntpi54l.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=spearce@spearce.org \
/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).