On Wed, May 18, 2011 at 1:27 PM, Nico Williams <n...@cryptonector.com>wrote:
> So I've stumbled twice trying to set up use of Fossil, both times with
> respect to how to create a private branch.
>
> First I did "fossil branch new ..." and didn't realize that the
> workspace was not switched to be in that branch, so that my subsequent
> commit didn't go to that branch.
>
> My second attempt I did "fossil branch new ..." then "fossil checkout
> ...", then "fossil commit ... --private", but the last command
> effectively created a new branch off my branch.
>
> My third attempt I did a "fossil commit --private --branch ...". That
> worked.
>
Thanks. That is good information for helping me write better documentation.
>
> 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.
>
> These are minor issues, IMO. I expected Fossil to be painful (most
> VCSes are), but aside from the above it's actually a pleasure.
> Thanks,
>
> Nico
> --
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
--
D. Richard Hipp
d...@sqlite.org
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
