Re: No actions delta file.
Donovan Baarda <[email protected]> Wed, 28 Sep 2005 10:50:22 +0100
| Newsgroups | gmane.network.librsync.general |
|---|---|
| Message-ID | <[email protected]> |
[ removing librsync-devel as this is a user issue ] On Tue, 2005-09-27 at 18:45, Carles Xavier Munyoz Baldó wrote: > > No. It will be very short though, as it should contain only a single > > "copy" command. > > Do you know where could I get documentation about the generated rsync delta > file, in order to discover this single "copy" command ? There is not much documentation on the delta file format. You would need to look at the code, and there are no guarentees that it won't change in future versions. > It is more efficient if I examine the generated delta file to see that it > contains a single "copy" command than generate another signature file or a > md5sum ;-) I would generate an md5sum or md4sum. At some stage in the future the signature and delta will include a whole-file md4sum for a variety of other reasons. The most efficient thing to do would be to use md5sum to generate a list of md5sums at both ends, then only calculate delta's for files that have changed... calculating a delta is heaps more work than calculating an md5sum. -- Donovan Baarda <[email protected]> ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl