Re: [fossil-users] Using doc/ckout from win service

2014-08-23 Thread Petr Ferdus
Od: Andy Bradford The distinction is that ckout only works with an open repository. Using Windows as a service does not use an open repository, so I wouldn't expect this to work. It might be possible for you to run the service from an open repository, but I'm not sure what the

Re: [fossil-users] Using doc/ckout from win service

2014-08-23 Thread Thomas Schnurrenberger
Hi Peter as the original author of the Windows service code, I probably can explain the behavior you are seeing. On 23.08.2014 09:13, Petr Ferdus wrote: I am not very clear, what specifically should I do to run service from open repository (while running fossil server args as server or the

[fossil-users] Tag appears in Timeline, but not in Timeline Tags Only

2014-08-23 Thread David Evans
In the repository at http://chiselapp.com/user/vinkix/repository/olrcix (cloneable URL) The timeline for 2014-08-20 19:29 shows a tag for RELEASE-1.6.14 In the Timeline Tags Only for this date, the tag is not shown. I have no idea why it does not show. It could be a bug in Fossil or it could

Re: [fossil-users] Tag appears in Timeline, but not in Timeline Tags Only

2014-08-23 Thread Richard Hipp
On Sat, Aug 23, 2014 at 9:38 AM, David Evans dave.evan...@googlemail.com wrote: In the repository at http://chiselapp.com/user/vinkix/repository/olrcix (cloneable URL) The timeline for 2014-08-20 19:29 shows a tag for RELEASE-1.6.14 In the Timeline Tags Only for this date, the tag is

Re: [fossil-users] Using doc/ckout from win service

2014-08-23 Thread Petr Ferdus
Thomas Schnurrenberger A service is never intended to serve a open checkout! It only serves Fossil repositories. Thank you for clarification. I have misunderstood doc/ckout purpose. Setting repository as a directory together with --files parameter suits my needs better. Anyone succeeded with

[fossil-users] Versionable settings question

2014-08-23 Thread Scott Robison
In the admin settings page it reads: Settings marked with (v) are 'versionable' and will be overridden by the contents of files named .fossil-settings/PROPERTY. If such a file is present, the corresponding field above is not editable. It seems that the fields are only uneditable if you use fossil