On 14 August 2013 19:23, Chad Perrin - c...@apotheon.net <
fossil.nrb.5c83664b76.code#apotheon....@ob.0sg.net> wrote:
> Is there some way to push the changed password to the remote repository
> so that it will be the Fossil repository password you'd use for that
> account next time you sync?
>
Would be useful to know. From an earlier mail, I recall that the other way
round is possible:
On 11 August 2013 12:03, Eduardo Morras - emorr...@yahoo.es <
fossil.nrb.bead472e5b.emorrasg#yahoo...@ob.0sg.net> wrote:
> User information is not cloned. If you want clone it from original server
> to cloned one you must use :
>
> fossil configuration pull user --overwrite original_repo_url
>
Then, looking at help for configuration it seems as though a Push version
is available:
fossil configuration pull AREA ?URL?
Pull and install the configuration from a different server
identified by URL. If no URL is specified, then the default
server is used. Use the --legacy option for the older protocol
(when talking to servers compiled prior to 2011-04-27.) Use
the --overwrite flag to completely replace local settings with
content received from URL.
fossil configuration push AREA ?URL?
Push the local configuration into the remote server identified
by URL. Admin privilege is required on the remote server for
this to work. When the same record exists both locally and on
the remote end, the one that was most recently changed wins.
Use the --legacy flag when talking to holder servers.
BR/ Nigel
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
