From mboxrd@z Thu Jan 1 00:00:00 1970 From: dexen deVries To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Date: Fri, 12 Aug 2011 09:50:32 +0200 User-Agent: KMail/1.13.6 (Linux/3.1.0-rc1-l36+; KDE/4.5.5; x86_64; ; ) References: <20110810220404.D6021B827@mail.bitblocks.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201108120950.32598.dexen.devries@gmail.com> Subject: Re: [9fans] simple venti demo: Topicbox-Message-UUID: 11fb063a-ead7-11e9-9d60-3106f5b1d025 On Thursday 11 of August 2011 18:15:09 ron minnich wrote: > Could we make little venti files and finally try to build an SCM using > these files? Venti would make a great backend for Git. I believe Git's commit and tree=20 format are simple enough to be re-implemented, if porting proves to be too= =20 bothersome. either the whole .git/ directory would be held in venti, or just the=20 =2Egit/objects/ -- the storage. =2D--- on the other hand, Git has that interesting feature that a bunch of recent= =20 commits is held in loose files, while older commits are re-packed into spac= e- efficient format using deltas.=20 was similar strategy ever considered for Venti? as in, to keep fresh data = in=20 present-day format, but migrate older data into denser format? =2D-=20 dexen deVries [[[=E2=86=93][=E2=86=92]]] =46or example, if the first thing in the file is: an XML parser will recognize that the document is stored in the traditional= =20 ROT13 encoding. (( Joe English, http://www.flightlab.com/~joe/sgml/faq-not.txt ))