The reason is NOT text files are small to enable only the binary files
working without text-base. The basic idea is that text files have
many special properties, such as svn:eol-style, svn:keywords, etc.,
which need special considerations. The process of text files would be
more complex than binary ones to achieve a same performance.
If time permitted, this is NOT a problem. But SoC is only 3 months.
Further more, small files may waste a lot of disk spaces in certain
systems. Working without text base is a charming feature.
In my mind, a rsync-like algorithm is a way to achieve this goal.
This is suggested in my revised proposal submitted to SoC.
On 5/14/06, Wesley J. Landaker <email@example.com> wrote:
> On Monday 08 May 2006 03:09, Qi Fred wrote:
> > - By specifying a special property on a certain file, one of the
> > three caching mechanisms can be chosen: original, compressed, and
> > excluded (caching disabled). Note that the text bases can be
> > excluded on client side only if the file is a binary one.
> I routinely deal with large (> 100 MiB) "text" files (EDIF, XML, etc). I
> wouldn't limit this to binary files on the assumption that "binary" files
> are big and "text" files are small.
> Wesley J. Landaker <firstname.lastname@example.org> <xmpp:email@example.com>
> OpenPGP FP: 4135 2A3B 4726 ACC5 9094 0097 F0A9 8A4C 4CD6 E3D2
Received on Sun May 14 17:30:29 2006