We probably need another flag. A dryrun shouldn't change any files on the local store.
Maybe just create an alias for fossil sync; fossil update -n ? I'm thinking of doing that in my emacs integration, but for across-the-world clients it will make the emacs operations so much slower. - Venkat -----Original Message----- From: Ron Wilson <[email protected]> Sent: Tuesday, August 30, 2011 13:04:50 Subject: Re: [fossil-users] dryrun option (-n) On Tue, Aug 30, 2011 at 11:43 AM, Richard Hipp <[email protected]> wrote:> > Is there any reason to "dryrun" a pull? Maybe we should make the > automatic pull happen even if the -n option is specified? > > Note that predicting what an "update" would do after a pull without > actually doing the pull first would be rather difficult. To me, it makes sense to do the pull even if a dry run is in progress. Doing a pull does not actually risk loosing any repository content. That said, I still would like pull to auto-detect forks. (I outlined a possible algorithm for this a while back.) _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
