From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: git-rev-list: make --dense the default (and introduce "--sparse")
Date: Wed, 26 Oct 2005 02:17:22 -0700 [thread overview]
Message-ID: <7vwtk08wnx.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0510251525540.10477@g5.osdl.org> (Linus Torvalds's message of "Tue, 25 Oct 2005 15:29:42 -0700 (PDT)")
Linus Torvalds <torvalds@osdl.org> writes:
> On Tue, 25 Oct 2005, Linus Torvalds wrote:
>>
>> This actually does three things:
>>
>> - make "--dense" the default for git-rev-list...
Heads up.
I have not looked closely into what exactly, but the fourth
thing this does might be to break git-send-pack.
I usually use the tip of "pu" myself, but for tonight, I am
excluding the fetch-pack/upload-pack changes from Johannes when
building git for my own use, and using somewhere in the middle
of "pu" branch. With this "--dense default" patch,
git-send-pack seems to send too few objects. With this patch
reverted, git-send-pack seems to work again.
+ [build] Revert "git-rev-list: make --dense the default (and introduce "--sparse")"
++ [pu^] Merge branch 'js-fat'
++ [pu^^2] Test in git-init-db if the filemode can be trusted
++ [pu~2] Merge branches 'cache-pack', 'lazy-subdir' and 'lt-dense'
++ [pu~2^4] git-rev-list: make --dense the default (and introduce "--sparse")
++ [pu~2^3] Create object subdirectories on demand (phase II)
++ [pu~2^2] Allow caching of generated pack for full cloning.
+++ [master] upload-pack: tighten request validation.
I'll take a look at the issue in the morning unless somebody
else beats me to it.
next prev parent reply other threads:[~2005-10-26 9:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-25 22:24 git-rev-list: make --dense the default (and introduce "--sparse") Linus Torvalds
2005-10-25 22:29 ` Linus Torvalds
2005-10-26 9:17 ` Junio C Hamano [this message]
2005-10-26 15:18 ` Linus Torvalds
2005-10-26 20:03 ` 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=7vwtk08wnx.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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