From: Linus Torvalds <torvalds@linux-foundation.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Make "git gc" pack all refs by default
Date: Thu, 24 May 2007 19:20:48 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.98.0705241911200.26602@woody.linux-foundation.org> (raw)
In-Reply-To: <7vy7jdu08k.fsf@assigned-by-dhcp.cox.net>
On Thu, 24 May 2007, Junio C Hamano wrote:
>
> Boy, you are a lot more aggressive than me.
Heh.
I don't like the http interfaces, so I have a much easier time saying
"they were broken, deal with it" ;)
I also think that we mis-calculated earlier in assuming that prople don't
have lots of branches, and that packing branches was thus much less
important than packing tags.
It's true that in sane git-only environment, you don't have lots of
branches (fifty isn't "lots"). But when importing things from other
environments, I seem to recall people talking about thousands of branches
(since they cannot be merged and they are project-wide rather than some
local entity, they cannot disappear).
So I think it's better to just pack branches aggressively too, and in
fact, once you do that, and http-fetch knows about it, then that also
means that info/refs becomes pointless, because afaik, it doesn't actually
contain anything more than what a modern "packed-refs" file contains.
So in order to take that _next_ step, we need to encourage people to pack
branches, and then at some point we can hopefully just make http-fetch
start ignoring info/refs..
So yeah, I think being aggressive here is a good idea. I really also
wanted to make update-server-info do the pack-refs thing, but to do it
properly we'd need to make the whole pack-refs thing have a nice library
interface, so it was a much bigger (although probably fairly
straightforward) thing.
Linus
prev parent reply other threads:[~2007-05-25 2:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 18:41 Make "git gc" pack all refs by default Linus Torvalds
2007-05-24 19:28 ` Johannes Schindelin
2007-05-25 2:04 ` Junio C Hamano
2007-05-25 2:20 ` Linus Torvalds [this message]
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=alpine.LFD.0.98.0705241911200.26602@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).