I expanded upon this some more.
-fixed some security concerns; fossil ui no longer is a bypass
-fixed an issue with access() and setuid logic
-the web interface has a place to change the posix id
-no need to manually modify tables
-changes contained within #ifdefs (exepct on the scheme.c part were
Remigiusz Modrzejewski wrote:
>On Oct 10, 2012, at 14:28 , Mike Meyer wrote:
>> Well, the lack of an in-binary API certainly isn't the reason there's
>not an Eclipse plugin. The Eclipse license is incompatible with the
>GPL, so any scm that's GPL'ed (*cough* git *cough*) isn't linked with
>Eclip
On Oct 10, 2012, at 14:28 , Mike Meyer wrote:
> Well, the lack of an in-binary API certainly isn't the reason there's not an
> Eclipse plugin. The Eclipse license is incompatible with the GPL, so any scm
> that's GPL'ed (*cough* git *cough*) isn't linked with Eclipse, but probably
> uses a pro
Remigiusz Modrzejewski wrote:
>>> Actually... No. Fossil, with it's monolithic single-app design, is
>>> relatively hard to both extend and embed.
>>
>> Actually there are two kinds of people in the world, those who expect
>> something to do whatever they think it should, and those who look at
Richard Hipp wrote:
[...]
> Worked ok here. What version of fossil do you have? What does "fossil
> version" tell you?
I'm on Debian, and am seeing it both the current release:
This is fossil version 1.22 [ab461f39af] 2012-03-29 08:48:38 UTC
...and from the upcoming release:
This is fossil ve
On Oct 9, 2012, at 20:44 , Eric wrote:
> On Tue, 9 Oct 2012 12:19:59 +0200, Remigiusz Modrzejewski
> wrote:
>>
>> But who would prevent a cow worker from using them?
>
> Cow worker
Reference to the Dilbert comics...
The idea is that, especially in corporate environments
6 matches
Mail list logo
