On Sun, Jun 1, 2014 at 3:32 PM, Michai Ramakers
wrote:
> trunk ([2a17ab66b2])
>
> repo RW, cfg-db RW:
>
repo RO, cfg-db RW:
>
> repo RW, cfg-db RO:
>
That all makes sense to me for the trunk version.
> close-cleanup-config branch ([43eeab7c52])
>
> repo RW, cfg-db RW:
>
> messag
Hello,
to avoid confusion, tested again.
- 'RO' means: owned root.wheel, perms 600
- 'RW' means: owned michai.users, perms 644
- only 'fossil close' was done with perms changed as below; all other
actions (i.e. checking status afterwards) was done with normal perms,
that is, RW for repo and cfg-d
On Sat, May 31, 2014 at 6:58 PM, Michai Ramakers
wrote:
> My test was a bit silly - repo perms were set 444, but owned
> michai.users, and executed as 'michai', sorry, let's do that again.
>
r/o should work, in the sense of it "shouldn't fail, but won't do much."
(For those who don't know 0444 =
On 31 May 2014 18:21, Stephan Beal wrote:
>
> i might have misunderstood some of the output, but my current understanding
> of "correct behaviour," adjusted for the assumption/assertion that the
> global config must be writable, is:
>
> - If the repo is read-only, it must silently fail to remove t
On Sat, May 31, 2014 at 6:11 PM, Michai Ramakers
wrote:
> On 31 May 2014 17:49, Stephan Beal wrote:
> >
> > On Sat, May 31, 2014 at 5:12 PM, Michai Ramakers
> >> I think indeed the 2nd test should close the repo, even if it can't
> >> update the config.
> >
> > i would have expected it to, actu
On 31 May 2014 17:49, Stephan Beal wrote:
>
> On Sat, May 31, 2014 at 5:12 PM, Michai Ramakers
> wrote:
>>
>> > b) repo is r/w but the global config is read-only
>> ...
>
> Okay, so... Fossil requires that .fossil be
> writeable, which means this whole test case is invalid vis-a-vis fossil's
> as
On Sat, May 31, 2014 at 5:12 PM, Michai Ramakers
wrote:
> ('f.f' is the repo; 'a' and 'b' are initially open roots):
>
> michai@main:~/fclose$ ls -l
> total 136
> drwxr-xr-x 2 michai users512 May 31 16:48 a
> drwxr-xr-x 2 michai users512 May 31 16:48 b
> -rw-r--r-- 1 michai users 5
On 31 May 2014 17:12, Michai Ramakers wrote:
>>
>> a) the repo is read-only
>
> ...
for completeness sake: the root at 'a' was closed as per 'fossil stat'
after calling 'fossil close' in that dir, when repo was r/o and global
config was r/w.
Michai
___
On 31 May 2014 16:26, Stephan Beal wrote:
>
> What happens to 'close' when:
>
> a) the repo is read-only
('f.f' is the repo; 'a' and 'b' are initially open roots):
michai@main:~/fclose$ ls -l
total 136
drwxr-xr-x 2 michai users512 May 31 16:48 a
drwxr-xr-x 2 michai users512 May 31 16
On Sat, May 31, 2014 at 4:01 PM, Michai Ramakers
wrote:
> That seems to work fine, thank you. I have merged this branch to trunk
> locally, and will continue to use it. If there are any things I can or
> should try/test here, let me know.
>
Great! i'm back from Augsburg but need to run out and d
On 30 May 2014 18:43, Stephan Beal wrote:
> On Fri, May 30, 2014 at 2:29 PM, Stephan Beal wrote:
>>
>> That's likely a misinteraction with the "all" setup and "close." When
>> fossil opens a repo db, it automatically records it in the global config db
>> for 'all' purposes. The close command "sho
No hurry - i won't be back on the pc until tomorrow evening. The wife's
attention takes priority, in any case!
"If at first I don't succeed... my wife will never let me forget it."
(recently heard in a video game)
(sent from a mobile device - please excuse brevity, typos, and top-posting)
-
On 30 May 2014 18:43, Stephan Beal wrote:
> On Fri, May 30, 2014 at 2:29 PM, Stephan Beal wrote:
>>
>> That's likely a misinteraction with the "all" setup and "close." When
>> fossil opens a repo db, it automatically records it in the global config db
>> for 'all' purposes. The close command "sho
On Fri, May 30, 2014 at 2:29 PM, Stephan Beal wrote:
> That's likely a misinteraction with the "all" setup and "close." When
> fossil opens a repo db, it automatically records it in the global config db
> for 'all' purposes. The close command "should" (but apparently doesn't?)
> remove that file
On 30 May 2014 14:29, Stephan Beal wrote:
> On Fri, May 30, 2014 at 2:24 PM, Michai Ramakers
> wrote:
>
>> I have only recently started using 'fossil all', and notice that
>> 'fossil all ls -c' (i.e. list checkouts) still show checkout-roots
>> that have been closed.
>
> That's likely a misintera
On Fri, May 30, 2014 at 2:24 PM, Michai Ramakers
wrote:
> a related issue has come up here at least one: is there any real use
> for 'fossil close' of a repo?
>
Rarely. i can count on one hand the number of times i've used it since
2008. You can get the same effect with:
rm -f .fslckout _FOSSIL
Hello,
a related issue has come up here at least one: is there any real use
for 'fossil close' of a repo?
I have only recently started using 'fossil all', and notice that
'fossil all ls -c' (i.e. list checkouts) still show checkout-roots
that have been closed.
I always used the 'close' command,
17 matches
Mail list logo
