On Nov 28, 2016, at 9:06 AM, Richard Hipp wrote:
>
>fossil all config pull all
Thanks, that’s perfect!
I care about this because I treat my local clones as off-site backups relative
to the official central repos, and it’s not a very good backup if it’s
incomplete.
I do realize that this
On 11/28/16, Warren Young wrote:
> I’ve noticed that if I make a change to a non-artifact setting in the
> repository on a different machine that re-syncing does not give me a copy on
> my machine.
>
> Examples:
>
> - Skin changes
> - Ticket tracker customizations
> - Everything in Admin > Setting
On Nov 26, 2016, at 1:26 PM, Martin Gagnon wrote:
>
> On Sat, Nov 26, 2016 at 01:15:11PM +0100, arnoldemu wrote:
>>
>> I forced a submit with
>>
>> fossil commit --allow-empty
>
> Server get the change here, because the "commit" command does a "sync"
> when autosync is enable (which is the def
I’ve noticed that if I make a change to a non-artifact setting in the
repository on a different machine that re-syncing does not give me a copy on my
machine.
Examples:
- Skin changes
- Ticket tracker customizations
- Everything in Admin > Settings
If I close the repo, re-clone, and reopen it
4 matches
Mail list logo