On Tue, Jan 14, 2014 at 10:35 PM, Andy Bradford amb-fos...@bradfords.orgwrote:
Hello,
While attempting to pull the Fossil repository, I saw this error:
$ fossil up
Autosync: https://www.fossil-scm.org/
Round-trips: 2 Artifacts sent: 0 received: 0
Error: Database error: database is
I set up the reader user so that (I thought) it could access things
needing read access.
When I put a link to ./doc/tip... something on my main repo page, I
found that having hyperlinks permission was not enough, but check
out permission was also required.
Is this correct behavior? It seems odd
On Wed, Jan 15, 2014 at 6:37 AM, Richard Hipp d...@sqlite.org wrote:
...t there is some common cleanup code that runs at the end of any pull or
push that does the UPDATE command above. The UPDATE is a no-op in the case
of a pull, but it runs nevertheless. Probably we should fix that.
On Wed, Jan 15, 2014 at 6:44 AM, Ron Aaron r...@ronware.org wrote:
I set up the reader user so that (I thought) it could access things
needing read access.
What are the capability characters you have assigned to reader.
The r and j capabilities are for reading tickets and wiki,
As of now, a reader has the capabilities bcfhjkmnoprtw
I guess you are right about the security difference, but I would like to
have a more fine-grained ability to allow access to (say) documents in a
certain folder to readers, but no access to the source code (or whatever).
On 01/15/2014 01:50
On Wed, Jan 15, 2014 at 6:54 AM, Ron Aaron r...@ronware.org wrote:
As of now, a reader has the capabilities bcfhjkmnoprtw
I guess you are right about the security difference, but I would like to
have a more fine-grained ability to allow access to (say) documents in a
certain folder to
Yes, thanks; I know about that, but that's too coarse-grained for my needs.
In this case, I have a project I want to be *non-public* altogether, but
I also don't want some people to have access to everything, and I can't
put everything in the wiki.
The current permission system works well, but
On Wed, Jan 15, 2014 at 6:44 AM, Ron Aaron r...@ronware.org wrote:
I set up the reader user so that (I thought) it could access things
needing read access.
When I put a link to ./doc/tip... something on my main repo page, I
found that having hyperlinks permission was not enough, but check
On Wed, Jan 15, 2014 at 6:54 AM, Ron Aaron r...@ronware.org wrote:
As of now, a reader has the capabilities bcfhjkmnoprtw
I guess you are right about the security difference, but I would like to
have a more fine-grained ability to allow access to (say) documents in a
certain folder to
On Wed, Jan 15, 2014 at 8:04 AM, Ron Aaron r...@ronware.org wrote:
Yes, thanks; I know about that, but that's too coarse-grained for my needs.
In this case, I have a project I want to be *non-public* altogether, but
I also don't want some people to have access to everything, and I can't
put
On Wed, Jan 15, 2014 at 7:58 AM, Richard Hipp d...@sqlite.org wrote:
Under Admin/Access the Public Pages entry box allows you to specify a
comma-separated list of GLOB patterns for file that will be visible to the
public even if the source code access is turned off. This is used, for
On Wed, Jan 15, 2014 at 11:36 AM, Ron Wilson ronw.m...@gmail.com wrote:
On Wed, Jan 15, 2014 at 7:58 AM, Richard Hipp d...@sqlite.org wrote:
Under Admin/Access the Public Pages entry box allows you to specify a
comma-separated list of GLOB patterns for file that will be visible to the
public
Hi
After this http://fossil-scm.org/index.html/info/1aef260f4c check-in I
cannot do incremental import anymore (I get the second dup trunk). An
imported git project is simple and has 'master' branch only. After that
I did revert this check-in the latest Fossil build does incremental
import for
Sergei Gavrikov wrote:
I found some inconsistencies on this (below is a delta for reference).
All the issues should be fixed now:
https://www.fossil-scm.org/index.html/vdiff?from=d0d7ca17a46a0832to=f61958b
183db741bsbs=1
Thanks again.
--
Joe Mistachkin
14 matches
Mail list logo
