From: Nicolas Pitre <nico@cam.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Theodore Tso <tytso@mit.edu>, Junio C Hamano <junkio@cox.net>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: git-gc "--aggressive" somewhat broken
Date: Sun, 08 Jul 2007 23:46:44 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0707082341460.26459@xanadu.home> (raw)
In-Reply-To: <alpine.LFD.0.999.0707061512550.8278@woody.linux-foundation.org>
On Fri, 6 Jul 2007, Linus Torvalds wrote:
>
>
> On Fri, 6 Jul 2007, Linus Torvalds wrote:
> >
> > If we want to be really aggressive, we migth decide to pass a new flag to
> > pack-objects that does something closer to what "aggressive" was meant to
> > do: it would use existing delta's if they exist, but _despite_ existing it
> > could look if there are even better choices.
>
> This is a totally untested patch that may or may not work.
>
> The reason I say "may not work" is not just that I haven't really tested
> it, it's also because I haven't thought it through very well.
>
> In particular, does this possibly cause infinite loops of delta chains?
> Probably. It would need code to explicitly make sure that we don't do
> that, but I couldn't even convince myself as to why we might not hit that
> case _already_ with delta re-use, so maybe there's something going that
> protects us against it.
There is.
> Anyway, consider this a starting point for somebody else who wants to
> really try to look into this.
This is a real teaser. But I have real work to do if I want to leave on
vacation this summer, and therefore I'll then be on vacation. So if I
end up looking at it myself it will be in September.
Nicolas
prev parent reply other threads:[~2007-07-09 3:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.0.999.0707061310390.8278@woody.linux-foundation.org >
2007-07-06 20:19 ` git-gc "--aggressive" somewhat broken Linus Torvalds
2007-07-06 22:17 ` Linus Torvalds
2007-07-07 1:16 ` Linus Torvalds
2007-07-09 3:46 ` Nicolas Pitre [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.999.0707082341460.26459@xanadu.home \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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).