On Wed, May 14, 2014 at 10:59 PM, Joseph Prostko wrote:
> suggested. In fact, I think I would prefer it.
suggested = implemented
I think I better head to sleep before I type anything else nonsensical
today. I was going to come up with a patch for this, but I think I
better call it a ni
On Wed, May 14, 2014 at 10:10 PM, Andy Goth wrote:
> On 5/14/2014 2:05 PM, Joseph Prostko wrote:
>> I've encountered the problem you mentioned about highlighting, but
>> admit I'm not sure if I'd like to see the brackets go away.
>
> I didn't suggest re
On Wed, May 14, 2014 at 2:38 PM, Andy Goth wrote:
> I'd like for the [bracket] characters to not be part of the ... links
> in Fossil web pages, at least when the link text is an artifact ID. This
> change would make it easier to highlight just the artifact ID and omit the
> brackets so that I ca
Okay, well just so everybody knows, after a couple of days of off-list
work, the problem is now resolved. Andy B. and Stephan both worked
hard with me to get this figured out, and now the fix has been merged
in as of this commit.
http://www.fossil-scm.org/index.html/info/5e47d555e4770445328a34f8a
On Tue, Apr 29, 2014 at 11:08 AM, Tony Papadimitriou wrote:
> This is fossil version 1.29 [09f2386328] 2014-04-28 12:24:17 UTC
>
> On a Win7 machine, during FOSSIL CHANGES command, I got this error
> “SQLITE_IOERR: delayed 25ms for lock/sharing conflict”
I "may" have seen this error happen on Hai
On Mon, Apr 28, 2014 at 1:05 PM, Stephan Beal wrote:
> i had no problems compiling, just had to find the lib path (it doesn't seem
> to support $LD_LIBRARY_PATH, which i tried first).
You could try $LIBRARY_PATH.
> - cloning and rebuild work. Or don't break.
>
> - ui (after setting 'web-browser
On Mon, Apr 28, 2014 at 12:34 PM, Stephan Beal wrote:
> Follow-up:
>
> Thanks to much off-list help from Joe, Fossil (current trunk 09f23863) is
> compiling and running for me on Haiku with no code changes (only one
> additional linker argument: -L/boot/system/lib before the -lsocket -lbsd
> flag
On Mon, Apr 28, 2014 at 6:34 AM, Stephan Beal wrote:
>
> On Mon, Apr 28, 2014 at 6:00 AM, Joseph Prostko
> wrote:
>>
>> actual commands like commit/update concerns the other developers. I guess
>> they've been spoiled by SourceTree, and don't want to do thos
On Sat, Apr 26, 2014 at 3:23 PM, Paulus Tuerah wrote:
> Hi all,
> Thanks for the great and the simplicity of Fossil (1 exe file without
> installation is really great).
> But unfortunately there is no GUI.
>
> Coming from SVN using Tortoise SVN, there is no way I will do version
> control with CL
On Sun, Apr 27, 2014 at 11:53 AM, Andy Bradford
wrote:
> Thus said Joseph Prostko on Sun, 27 Apr 2014 10:42:01 -0400:
>
>> invalid home directory: /boot/home
>
> Fossil thinks this isn't a home directory, please provide:
>
> echo $HOME
> ls -ld /boot/home
(Just
On Sun, Apr 27, 2014 at 7:40 PM, Stephan Beal wrote:
> Thanks for the additional details. i looked at haiku several years ago (and
> way back in 98 or 99), but have never done anything but boot it up and click
> around. Sounds like Pe will be my first stop (my fingers simply refuse to
> learn vi p
On Sun, Apr 27, 2014 at 1:35 PM, Stephan Beal wrote:
> On Sun, Apr 27, 2014 at 6:14 PM, Joseph Prostko
> wrote:
>>
>> http://haiku-files.org/haiku/development/ which will work in
>> VirtualBox. Just make sure to use the Intel IPro100 adapter for
> Great - thanks f
On Sun, Apr 27, 2014 at 11:11 AM, Stephan Beal wrote:
> On Sun, Apr 27, 2014 at 4:42 PM, Joseph Prostko
> wrote:
>>
>> Thanks for any advice on helping to explain what is going on with
>> respect to the code execution path. I still plan on getting better
>> acq
Hello,
I am involved with the Haiku operating system project, and as such,
have lately been going through some software that personally interests
me (PHP, Nginx, and Fossil in particular) in order for us to have
packages available for our package management system.
In any case, some bugs got fixe
On Wed, Apr 2, 2014 at 2:56 AM, Jan Nijtmans wrote:
> 2014-04-02 2:24 GMT+02:00 Joseph Prostko :
>> Below is a patch via `fossil diff` to detect getloadavg() which allows
>> Fossil to build cleanly on Haiku (and potentially other systems that
>> would happen not to have g
On Tue, Apr 1, 2014 at 8:24 PM, Joseph Prostko wrote:
> Below is a patch via `fossil diff` to detect getloadavg() which allows
> Fossil to build cleanly on Haiku (and potentially other systems that
> would happen not to have getloadavg() available.
My mail client wrapped text, unfo
Hello,
I was trying to build a recent version of Fossil on Haiku, and noticed
that the build failed due to there not being getloadavg() on the
platform.
Below is a patch via `fossil diff` to detect getloadavg() which allows
Fossil to build cleanly on Haiku (and potentially other systems that
woul
On Mon, Mar 31, 2014 at 1:32 PM, Stephan Beal wrote:
> Done - please update. Richard made a change which was easy to do with global
> copy/replace but he could not have seen this particular usage because it was
> generated by a macro (and he doesn't build in json mode, so it compiled for
> him).
On Mon, Mar 31, 2014 at 1:27 PM, Stephan Beal wrote:
> i'll fix that - caused by a recent internal change.
Thank you, Stephan!
- joe
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listin
Hello,
I was just building the newly-committed 5fdad9bd8c, and I noticed that
when configured/built with --json, the build does not go to
completion.
cc -DFOSSIL_ENABLE_JSON-g -O2 -DHAVE_AUTOCONFIG_H -I. -I./src
-Ibld -o bld/json.o -c bld/json_.c
./src/json.c: In function 'json_g_to_json':
On Sun, Mar 23, 2014 at 10:03 AM, Jon wrote:
>> Also, I'm going to experiment with Upstart a bit now due to this
>> thread. I admit I've always been an init script kind of guy, but it
>> doesn't hurt to try something new when it is supported on your
>> platform.
>
> re: the future of upstart on
On Sat, Mar 22, 2014 at 6:23 PM, Jon wrote:
> With a fresh build of 684eb478e my SCGI setup with nginx 1.5.12 on
> Ubuntu Server 13.10 64bit appears to be working.
>
> Fossil is started via upstart using:
>
> exec /usr/local/sbin/fossil server --localhost --scgi /srv/fossils/partner
>
> Nice cat
On Sat, Mar 22, 2014 at 7:34 AM, Richard Hipp wrote:
> Your patch has been applied. Thanks for tracking this down.
Not a problem. Fortunately it didn't take too long to track down
since I started binary searching on cgi.c itself instead of the entire
codebase like I normally would. The only tw
Hello,
I am running Nginx 1.5.12, and noticed that Fossil 1.28 fails to work
when set up to run via SCGI. SCGI works fine with Fossil 1.27, and
after doing a binary search, I concluded definitively that 63a84cb66e
from 2014-10-17 is the culprit.
To be extra thorough, I tried Nginx 1.0.15, 1.2.9,
24 matches
Mail list logo
