Lines Matching full:changes

80 changes to the other system. Once this has been done, the two copies are,
83 If a source file has changed and the destination file has not, the changes on
85 file has changed and the corresponding source file has not, the changes on the
160 minor changes, it is probably easier to just edit \fB$HOME/.packingrules\fR.
161 For major changes it is probably easier to start from scratch.
235 The \fB-f\fR option tells \fBfilesync\fR how to resolve conflicting changes. If
237 specified, \fBfilesync\fR will retain the changes made on the favored system
238 and discard the changes made on the unfavored system.
272 by default. File changes are ordered by increasing modification times so that
274 original changes. Users should be warned that there is usually some time skew
292 Do not really make the changes. If the  \fB-n\fR option is specified,
293 \fBfilesync\fR determines what changes have been made to files, and what
295 output. No changes are made to files, including the packing rules file.
298 analyze the prevailing system and report the changes that have been made on
301 what changes have been made on the local machine. See the \fB-o\fR option
314 Specify \fB-o\fR \fBsrc\fR to propagate changes only from the source system to
315 the destination system. Changes made on the destination system are ignored.
318 Specify \fB-o\fR \fBdst\fR to propagate changes only from the destination
319 system to the source system. Changes made on the source system are ignored.
323 the prevailing system and reports on what changes have been made on that
326 changes have been made on the local machine. See the \fB-n\fR option
390 asked to reconcile local changes against the wrong file system or server. This