Quoth Jan Hendrik <mailto:jan.hendrik@myrealbox.com>:
> The point, however, is that *all* FTP synching has to done from the
> *same* WC - all the other WCs have timestamps different from
> those on the webserver (checkout/commit time).
>
> So if for any reason an FTP synch is to be done from another WC
> local timestamps first have to be adjusted to remote timestamps or
> FTP synch would consider *all* files as modified. Afterwards FTP
> will still indicate files that are different (more exactly:
> that have a
> different filesize), but SVN will not commit any file anymore that
> was not committed before FTP synch, no matter if the filesize had
> changed or not (the typo thing where filesize does not change
> either is a special case).
That shouldn't be too much of a problem, since you should be committing
to SVN before uploading to the FTP anyway.
If you want to persist in this behaviour, then I'd recommend the
following strategy instead:
1. When FTP Sync is used to upload the files to the FTP server, note
down the revision number of the working copy at the time.
2. When you want to update the files on the server, and for whatever
reason you must use a different working copy, then do this:
2a. Make sure you've committed all changes that you've made
2b. Update your working copy to the *same* revision as was uploaded to
the FTP server
2c. Use your FTP Sync program to set all local timestamps equal to the
remote ones
2d. Update the working copy to the revision you want to upload (probably
HEAD)
2e. Use your FTP Sync program to do the actual upload
The update in #2d might take a little while, since it'll see the wrong
timestamps and have to do a content scan, but at the end of it you
should get a working copy where the timestamps differ only for modified
files. At least as long as the update doesn't reset the timestamps on
unmodified files, but I don't think it does.
But I basically agree with Jeff. Trying to use two different version
controlling methods on the same directory would get fairly painful.
(Besides, using timestamps as your only means of detecting modifications
is fragile, which is why SVN doesn't do it -- what happens if one
computer has the wrong date set?)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 16 01:46:06 2007