From: Jeff King <peff@peff.net>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>,
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 05:43:40 -0400 [thread overview]
Message-ID: <20130810094339.GB2518@sigill.intra.peff.net> (raw)
In-Reply-To: <CACsJy8DtiSupsvDgeBXGGnGE06pDxWvYTNrk3bpta9Bwk5MZwg@mail.gmail.com>
On Sat, Aug 10, 2013 at 04:24:48PM +0700, Nguyen Thai Ngoc Duy wrote:
> > Yeah, I read about the --thin option. However, it's only for
> > network-packs (i.e --stdout; why?). Also, is it turned on by default?
> > The documentation says so, but I ran it and found that the value of
> > thin is 0 in builtin/push.c:316. What is going on?
>
> --thin is enabled by default for fetch (see
> transport.c:transport_get()) but it's only effective when the server
> advertises "thin-pack" capability (see protocol-capabilities.txt).
> push has --thin turned off by default favoring server resources over
> network traffic, see a4503a1 (Make --no-thin the default in git-push
> to save server resources - 2007-09-09)
Hmm. I don't think that is the case anymore.
If I do:
git init parent &&
(cd parent && seq 1 10000 >file &&
git add file && git commit -m base
) &&
git clone parent child &&
cd child && seq 1 10001 >file &&
git commit -a -m more &&
GIT_TRACE=1 git push origin HEAD:foo
I see:
trace: run_command: 'pack-objects' '--all-progress-implied' '--revs'
'--stdout' '--thin' '--delta-base-offset' '--progress'
-Peff
next prev parent reply other threads:[~2013-08-10 9:43 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 [this message]
2013-08-10 9:50 ` Duy Nguyen
2013-08-10 10:05 ` Ramkumar Ramachandra
2013-08-10 10:16 ` Duy Nguyen
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=20130810094339.GB2518@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mfick@codeaurora.org \
--cc=pclouds@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).