Thanks for your reply, Ryan. On Mon, 4/26/10, Ryan Schmidt <subversion-20...@ryandesign.com> wrote: > Changed since when? Changed since the last deployment. The routine would send the file sizes of the files on the deployed computer to the repository server, and if the file sizes differed from the file sizes of the given revision (the current revision by default), the server would send the updated file to the deployed computer.
> I think > you'll be better off using existing solutions to this > problem, such as rsync from a local svn export to your > remote deployment, or even simply making your remote > deployment a working copy and using svn update there. My client is aware of rsync utility, but would prefer to use svn. I'll have to correspond with her to find out why she doesn't want to use rsync. As far as making the remote deployment a working folder and using svn update, she doesn't want to have the clutter of the hidden .svn folders on the deployed computers. For anyone who's interested, the details of the project I'm working on can be found at www.rentacoder.com/RentACoder/misc/BidRequests/ShowBidRequest.asp?lngBidRequestId=1395905 Here my client gives the use cases for the feature she's looking for. I'll speak with her about the suggestions I got here and relay her responses on this mailing list. Thanks, --Paul Breen
