2014/1/13 Mark Janssen mpc.jans...@gmail.com:
I am not sure if this is an issue with my MinGW install, but latest trunk
fails to build on MinGW. I think it's useful if the official release can
also be built on MinGW.
http://fossil-scm.org/index.html/info/354288db9c
Thanks!
Jan
Hallo to the list. I am a newby and not sure, this is the right place to ask my
question.
Anyway my problem is, I have closed a leaf, which I did not have to close. Now if I try to commit
against my repository, I get the message: cannot commit against a closed leaf. Is there a way to
re-open
On Tue, Jan 14, 2014 at 9:36 AM, Jan Nijtmans jan.nijtm...@gmail.comwrote:
2014/1/13 Mark Janssen mpc.jans...@gmail.com:
I am not sure if this is an issue with my MinGW install, but latest trunk
fails to build on MinGW. I think it's useful if the official release can
also be built on
2014/1/14 Joseph R. Justice jayare...@gmail.com:
(I also note from the timeline that
the prospective 1.28 does appear to have a release version of SQLite
embedded.)
Actually, branch-1.28 doesn't contain a release version of
SQLite either, it contains the most stable version. This is
almost the
2014/1/14 Mark Janssen mpc.jans...@gmail.com:
With that commit, build still fails on sqlite.c:
src/sqlite3.c:34515: warning: implicit declaration of function
'winShmMutexHeld'
Should be fixed now in branch-1.28. In trunk it should be
fixed as soon as a new SQLite amalgamation appears there.
Thus said Jan Nijtmans on Tue, 14 Jan 2014 10:33:57 +0100:
And the last one which doesn't affect fossil
at all because fossil doesn't use fork():
https://www.mail-archive.com/sqlite-users@sqlite.org/msg81284.html
Technically it does use fork() for SSH sync operations but I don't
Thus said Pierluigi Moschetti on Tue, 14 Jan 2014 10:01:18 +0100:
I get the message: cannot commit against a closed leaf. Is there a
way to re-open the leaf? I tried to edit the item in the timeline
where Closed-leaf is shown, but I did not find any command to set
the leaf to open
Joel - thanks for trying to fix this problem. But your patch doesn't
work. On Chrome Version 31.0.1650.63 (the default on Ubuntu 13.10)
pressing the back button returns to a collapsed tree. And on IE10, it no
longer expands when clicking on a directory. (Firefox and Safari work in
all cases
Richard Hipp wrote:
Joel - thanks for trying to fix this problem. But your patch doesn't
work. On ChromeVersion 31.0.1650.63 (the default on Ubuntu 13.10)
pressing the back button returns to a collapsed tree. And on IE10, it
no longer expands when clicking on a directory. (Firefox and
Joel Bruick wrote:
Sorry, I shouldn't have committed it to trunk in the first place. I'll
let you know when I've got it working better.
Should be working properly now. Tested on Firefox, Chrome, and IE10/11.
___
fossil-users mailing list
On Tue, Jan 14, 2014 at 8:42 PM, Joel Bruick j...@joelface.com wrote:
Joel Bruick wrote:
Sorry, I shouldn't have committed it to trunk in the first place. I'll let
you know when I've got it working better.
Should be working properly now. Tested on Firefox, Chrome, and IE10/11.
Brilliant!
Hello,
While attempting to pull the Fossil repository, I saw this error:
$ fossil up
Autosync: https://www.fossil-scm.org/
Round-trips: 2 Artifacts sent: 0 received: 0
Error: Database error: database is locked: {UPDATE event SET mtime=(SELECT m1
FROM time_fudge WHERE mid=objid) WHERE objid
On 1/14/14, Andy Bradford amb-fos...@bradfords.org wrote:
Hello,
While attempting to pull the Fossil repository, I saw this error:
$ fossil up
Autosync: https://www.fossil-scm.org/
Round-trips: 2 Artifacts sent: 0 received: 0
Error: Database error: database is locked: {UPDATE event SET
Thus said B Harder on Tue, 14 Jan 2014 19:38:55 -0800:
No pending commits in other windows? (ie: waiting for you to enter
password for gpg key) ?
No, and in fact, this was the first time I ran any fossil command after
logging in and ps did not show any other fossil commands.
I wonder if
14 matches
Mail list logo
