DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
	b=AfiEnG8RU282v1tEp04GFyifNsJTJI4I/ooSHsJr/CTBNc94XuteVjigUEy4/ryT4AcLHoAmi9BTXwBgLUtS/63gh1a68T+5n2j+UZNzOUKvwCPuJixGHJ4Ex2pmSrDGA01dD/VxL0MrQ0FssKp1SauAabsO+M/rfKMQWaNJulg=
Message-ID: <fc339e4a04111805243d86056c@mail.gmail.com>
Date: Thu, 18 Nov 2004 22:24:40 +0900
From: Miles Bader <snogglethorpe@gmail.com>
To: Anand Kumria <wildfire@progsoc.org>
Subject: Re: [Gnu-arch-users] cacherev policy script
In-Reply-To: <pan.2004.11.18.13.23.45.365921@progsoc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <pan.2004.11.18.13.23.45.365921@progsoc.org>
Cc: gnu-arch-users@gnu.org
Precedence: list
Reply-To: snogglethorpe@gmail.com, miles@gnu.org
Sender: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Errors-To: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Status: RO
Content-Length: 749
Lines: 20
> it talks says an optimal cacherev policy would be "cached revisions such
> that the sum of the sizes of changesets between any two cached revisions
> is about the same as the size as the [...] cached revision."

Not really "optimal" for all purposes -- e.g., in my emacs branch,
there are currently over 700 revisions, but the total size of all
those changesets is still less than a single emacs cacherev... 
However for purposes of not driving people doing virgin checkouts
nuts, more frequent cacherevs are called for.

-Miles


_______________________________________________
Gnu-arch-users mailing list
Gnu-arch-users@gnu.org
http://lists.gnu.org/mailman/listinfo/gnu-arch-users

GNU arch home page:
http://savannah.gnu.org/projects/gnu-arch/