From: Duy Nguyen <pclouds@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>,
Martin Fick <mfick@codeaurora.org>,
Git List <git@vger.kernel.org>
Subject: Re: [PATCH] git exproll: steps to tackle gc aggression
Date: Sat, 10 Aug 2013 17:16:00 +0700 [thread overview]
Message-ID: <CACsJy8AnY0pgHSxYDvqLonojGxSyAXUCGwzWwuZWQRVwAVnsFg@mail.gmail.com> (raw)
In-Reply-To: <CALkWK0=cZyKO7tjjtgE+tvwkkHGN7xLUy0uKHwXd8zkrM7o2Wg@mail.gmail.com>
On Sat, Aug 10, 2013 at 5:05 PM, Ramkumar Ramachandra
<artagnon@gmail.com> wrote:
> Duy Nguyen wrote:
>> Right. transport_get() is also run for push and it sets
>> smart_options->thin = 1 unconditionally.
>
> So, it looks like smart http implies the thin capability.
"smart_options" is a bit misleading. This applies to both smart
http://, git:// and ssh://
> I think
> sop's patch (6 years ago) was about turning off thin on dumb http
No, dumb http walks through the remote repository object database,
there's no temporary pack created for transferring data. Dumb http has
nothing to do with this flag.
--
Duy
next prev parent reply other threads:[~2013-08-10 10:16 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 2:38 [PATCH] git exproll: steps to tackle gc aggression Ramkumar Ramachandra
2013-08-06 12:24 ` Duy Nguyen
2013-08-06 17:39 ` Junio C Hamano
2013-08-07 4:43 ` Ramkumar Ramachandra
2013-08-08 7:13 ` Junio C Hamano
2013-08-08 7:44 ` Ramkumar Ramachandra
2013-08-08 16:56 ` Junio C Hamano
2013-08-08 17:34 ` Martin Fick
2013-08-08 18:52 ` Junio C Hamano
2013-08-08 19:14 ` Ramkumar Ramachandra
2013-08-08 17:36 ` Ramkumar Ramachandra
2013-08-08 19:37 ` Junio C Hamano
2013-08-08 20:04 ` Ramkumar Ramachandra
2013-08-08 21:09 ` Martin Langhoff
2013-08-09 11:00 ` Jeff King
2013-08-09 13:34 ` Ramkumar Ramachandra
2013-08-09 17:35 ` Junio C Hamano
2013-08-09 22:16 ` Jeff King
2013-08-10 1:24 ` Duy Nguyen
2013-08-10 9:50 ` Jeff King
2013-08-10 5:26 ` Junio C Hamano
2013-08-10 8:42 ` Ramkumar Ramachandra
2013-08-10 9:24 ` Duy Nguyen
2013-08-10 9:28 ` Duy Nguyen
2013-08-10 9:43 ` Jeff King
2013-08-10 9:50 ` Duy Nguyen
2013-08-10 10:05 ` Ramkumar Ramachandra
2013-08-10 10:16 ` Duy Nguyen [this message]
2013-08-10 9:38 ` Jeff King
2013-08-07 0:10 ` Martin Fick
2013-08-08 2:18 ` Duy Nguyen
2013-08-07 0:25 ` Martin Fick
2013-08-07 4:36 ` Ramkumar Ramachandra
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=CACsJy8AnY0pgHSxYDvqLonojGxSyAXUCGwzWwuZWQRVwAVnsFg@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mfick@codeaurora.org \
--cc=peff@peff.net \
/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).