From: Nicolas Pitre <nico@cam.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Linus Torvalds <torvalds@osdl.org>, git@vger.kernel.org
Subject: Re: [PATCH] mkdelta enhancements
Date: Thu, 26 May 2005 08:44:50 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.62.0505260840420.16151@localhost.localdomain> (raw)
In-Reply-To: <7vll62egoe.fsf@assigned-by-dhcp.cox.net>
On Wed, 25 May 2005, Junio C Hamano wrote:
> I have not measured and I have not studied how the current
> mkdelta does things, but if you are not doing so already it may
> make sense to keep the later one expanded in full and represent
> older ones as delta, since that would give faster access to more
> often used items (I am assuming more recent version are likely
> to be accessed more frequently, which I believe is what SCMs
> typically do.
This is precisely what is done with git-deltafy-script.
The mkdelta program doesn't know about object history. It only enforce
delta precedence according to the order objects are listed on the
command line. It's up to mkdelta users to enforce any ordering policy.
Nicolas
prev parent reply other threads:[~2005-05-26 12:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-26 3:57 [PATCH] mkdelta enhancements Nicolas Pitre
2005-05-26 4:48 ` Junio C Hamano
2005-05-26 12:44 ` 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=Pine.LNX.4.62.0505260840420.16151@localhost.localdomain \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--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;
as well as URLs for NNTP newsgroup(s).