On Wed, May 18, 2011 at 9:50 PM, Richard Hipp <d...@sqlite.org> wrote: > On Wed, May 18, 2011 at 1:27 PM, Nico Williams <n...@cryptonector.com>wrote: >> Also, I didn't expect commits and branches to go to the repository >> that I cloned mine from. That was surprising! With git and other >> similar VCSes such operations only hit the repository from which the >> workspace was checked out. Is this a configuration issue? > > That's a feature, called "autosync". You can turn it off like this: > > fossil setting autosync off > > When autosync is on (the default), Fossil tries to "pull" before each update > or checkout or commit, and it tries to "push" after each commit. It does > this push or pull against the last repository you synced with, or against > the repo that you cloned from if you have never synced before.
You might want a way to set this on the clone command, or else to mention this where fossil clone is covered. Is a "private" branch then one for which autosync is off, or is there some other distinction as well? How does one change a branch to no longer be private? How does one remove changesets? How does one collapse deltas? Thanks, Nico -- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
