[email protected] wrote:
Revision: 11267
http://harbour-project.svn.sourceforge.net/harbour-project/?rev=11267&view=rev
Author: vszakats
Date: 2009-06-08 09:11:25 +0000 (Mon, 08 Jun 2009)
Log Message:
-----------
2009-06-08 11:05 UTC+0200 Viktor Szakats (harbour.01 syenar.hu)
* ChangeLog
+ ChangeLog-old
+ Created ChangeLog-old which currently holds entries
belonging to 1.0.1 and older versions, moved from main
ChangeLog. From time to time we should move additional
entries there from main ChangeLog to not let main
ChangeLog grow too large. Updating files causes SVN dumps
to contain the whole file each time it's changed, which
means a large ChangeLog has a dramatic effect on the
size of the SVN dump. We're at 12.4GB at this moment,
much of this is ChangeLog copies (about ~4000 of them).
Hi,
finally I've found the text "on the paper", I has somethere deep inside
my memory. Here is the real solution:
http://svnbook.red-bean.com/en/1.5/svn-book.pdf page 141:
By default, the dump file will be quite large—much larger than the
repository itself. That's because by default every version of every file
is expressed as a full text in the dump file. This is the fastest and
simplest behavior, and it's nice if you're piping the dump data directly
into some other process (such as a compression program, filtering
program, or loading process). But if you're creating a dump file for
longer-term storage, you'll likely want to save disk space by using the
--deltas option. With this option, successive revisions of files will be
output as compressed, binary differences—just as file revisions are
stored in a repository. This option is slower, but it results in a dump
file much closer in size to the original repository.
Regards,
Mindaugas
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
