On 12/9/05, Gavin Lambert <firstname.lastname@example.org> wrote:
> Quoth Oscar Fuentes <>:
> > Whenever I commit changes on certain file a bloated commit
> > file is created on the db/revs directory. I say bloated
> > because the committed file contains ASCII text and the diff
> > wrt previous commit is just a few short lines (typically 10
> > lines totalling approx 200 chars). The committed file size is
> > 44 KB and the corresponding rev file is 38 KB. On a
> > repository of about 800 files, this is the only file that
> > shows the problem. As this file is changed often, a large
> > part of the repository size is due to this problem.
> > The only reason I can think about is that the original commit
> > could have UNIX line endings and successive commits contains
> > DOS line endings. I would expect a somewhat large rev file
> > when the file changed from UNIX to DOS line endings, but once
> > the conversion was committed, I expect a rev file size
> > proportional to the changes relative to previous commit.
> Could also be getting committed as binary. Check the file's info to see
> whether it's listed as a text file or a binary file.
Subversion doesn't make the distinction between binary and text-files
when storing file-contents. It only does that when
> If it's marked as a binary file and you don't think it should be, then
> check whether the file is plain ASCII or whether it's been saved as
> UTF8. I don't think Subversion handles UTF8 or Unicode files properly
> yet. Though I could be wrong.
All files are stored by calculating binary deltas, so, this shouldn't
be the cause of the problem. It may be something in the structure of
the files which causes the to be stored more verbosely than expected,
Received on Fri Dec 9 10:52:58 2005