Thus said B Harder on Sun, 01 Jun 2014 22:42:39 -0700:
> I think drh unnecessarily missed an opportunity there. He seemed to
> work harder to obfuscate what fossil actually was than giving a single
> passing description and moving on with his talk about SQL and using
> fossil by name where i
I think drh unnecessarily missed an opportunity there. He seemed to work
harder to obfuscate what fossil actually was than giving a single passing
description and moving on with his talk about SQL and using fossil by name
where it's used as an example.
Otherwise, interesting talk!
On Jun 1, 2014 8
Thus said =?UTF-8?B?RMO2bcO2dMO2ciBHdWx5w6Fz?= on Sun, 01 Jun 2014 12:56:41
+0200:
> An interesting scenario, what is there to be learned from it for
> fossil? Since fossil doesn't like history rewrites, are we protected
> to some degree from falsified commits?
With our without PGP signi
On Sun, Jun 1, 2014 at 5:20 PM, Joel Bruick wrote:
> I just wanted to share Richard's PGCon 2014 keynote for anyone here that
> wasn't aware of it:
>
Thanks for sharing that. And it was good to hear an entire presentation
about SQL without once (that I can recall) hearing it pronounced "sequel".
I just wanted to share Richard's PGCon 2014 keynote for anyone here that
wasn't aware of it:
https://www.youtube.com/watch?v=ZvmMzI0X7fE
It's a great talk about the historical relationship between SQLite and
PostgreSQL as well as a celebration of the usefulness of SQL. Richard
goes through se
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 Sun, Jun 1, 2014 at 1:35 PM, Stephan Beal wrote:
>
> So, yes, it seems it is doable with a bit of hacking on the
> above-mentioned config page.
>
Or, much more simply: hard-code a link to your report in that page,
somewhere above (or in) the block which outputs $report_items. It'll
be shown
On Sun, Jun 1, 2014 at 1:27 PM, Paolo Bolzoni wrote:
> It is possible to reoder the ticket report format?
> I made a new one that hides the Fixed issuesa
> and I would like to show it first.
>
i think what you want is: Admin ==> Tickets ==> Report List Page
Hm. But that requires building the li
Dear list,
It is possible to reoder the ticket report format?
I made a new one that hides the Fixed issuesa
and I would like to show it first.
Yours sincerely,
Paolo
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm
An interesting scenario, what is there to be learned from it for
fossil? Since fossil doesn't like history rewrites, are we protected
to some degree from falsified commits? (I ask as I have not yed had
the opportunity to look into fossil's security features extensively)
On 1 June 2014 06:43, B Har
On Sun, Jun 1, 2014 at 9:26 AM, Michai Ramakers
wrote:
> Thanks a lot. As you already suggested, initial checkin now being the
> default again, the initial-checkinless feature will probably receive
> precious little testing, let alone from new users.
>
It will from me, because libfossil doesn't
On 31 May 2014 21:40, Stephan Beal wrote:
> On Sat, May 31, 2014 at 4:33 PM, Stephan Beal wrote:
>>
>> Once i'm back from shopping i'll work on a patch which reverts to
>> ...
>
> i've implemented the above. It looks something like:
> ...
Thanks a lot. As you already suggested, initial checkin n
13 matches
Mail list logo
