[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Compressed text-base, take 2

From: Eric Dorland <eric.dorland_at_mail.mcgill.ca>
Date: 2003-05-14 23:02:14 CEST

* cmpilato@collab.net (cmpilato@collab.net) wrote:
> Kean Johnston <jkj@sco.com> writes:
>
> > Eric Dorland wrote:
> > > I decided not to put a compressed property in the entries file, since
> > > I think it's more flexible this way (ie, you will be able to go into
> > > the .svn/text-base dir and gzip * and it will just work), and putting
> > > it in the entries would further complicate the code IMHO. But if there
> > > are still advantages I'm not seeing, I'm all ears.
> > I just have one question: if I have a binary file that happens to end in
> > .gz I assume everything will be safe?
> >
> > I've never actually used binary files in my svn tests yet, so I dont
> > even know if they even make their way into the text base but if they
> > do, you'd better make sure that your scheme does not erroneously
> > detect that as a file I manually decided to gzip to save space.
>
> Looks like his patch will add the .gz to the already-extended
> text-base name. So you file "tarball.gz" will have a text-base named
> either "tarball.gz.svn-base.gz" or "tarball.gz.svn-base", depending on
> whether or not your are compressing textbases.

Exactly right.

-- 
Eric Dorland <eric.dorland@mail.mcgill.ca>
ICQ: #61138586, Jabber: hooty@jabber.com
1024D/16D970C6 097C 4861 9934 27A0 8E1C  2B0A 61E9 8ECF 16D9 70C6
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GCS d- s++: a-- C+++ UL+++ P++ L++ E++ W++ N+ o K- w+ 
O? M++ V-- PS+ PE Y+ PGP++ t++ 5++ X+ R tv++ b+++ DI+ D+ 
G e h! r- y+ 
------END GEEK CODE BLOCK------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 14 23:04:06 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.