On Thu, Jan 21, 2016 at 4:39 PM, Richard Hipp wrote:
> On 1/21/16, Baruch Burstein wrote:
> >
> > If fossil is compiled without fuse
> > support, ... It also
> > shouldn't show up in the listing of "fossil help".
>
> That could be fixed (probably) by
On Tue, Jan 26, 2016 at 8:15 AM, Baruch Burstein
wrote:
> Is there any special reason not to treat fusefs the same as json (which is
> completely removed if compiled without json support, and "fossil json"
> gives "command not found" and not "not implemented in this
On Thu, Jan 21, 2016 at 3:16 PM, Richard Hipp wrote:
> On 1/21/16, Stephan Beal wrote:
> > Hiho,
> >
> > since this is pending review...
> >
> > http://www.fossil-scm.org/index.html/info/06fd798bdcb9da50
> >
> > FYI: that won't compile properly on some
Hiho,
since this is pending review...
http://www.fossil-scm.org/index.html/info/06fd798bdcb9da50
FYI: that won't compile properly on some systems because C does not allow
an empty compilation unit, which is what that amounts to when fuse is
disabled. (i had a similar proble
Personally i prefer
On 1/21/16, Stephan Beal wrote:
> Hiho,
>
> since this is pending review...
>
> http://www.fossil-scm.org/index.html/info/06fd798bdcb9da50
>
> FYI: that won't compile properly on some systems because C does not allow
> an empty compilation unit, which is what that amounts
On 1/21/16, Baruch Burstein wrote:
>
> If fossil is compiled without fuse
> support, ... It also
> shouldn't show up in the listing of "fossil help".
That could be fixed (probably) by omitting "fusefs" from the "fossil
help" listing on systems where fusefs is not supported,