On Wed, May 7, 2014 at 8:15 AM, Stephan Beal sgb...@googlemail.com wrote:
The lock you're seeing is almost certainly your dropbox and should be
harmless. sqlite locks the db as needed, and Dropbox should recognize
that and not touch the file as long as it's locked (but posix locks are
2014-05-01 12:28 GMT+02:00 Stephan Beal sgb...@googlemail.com:
No objections, but some comments...
- libfossil has been using repos without an initial commit since last
summer. AFAIK there are no more open assertions related to that, but every
now and then i'll run into a case which expects
Thus said Jan Nijtmans on Thu, 08 May 2014 12:29:27 +0200:
Well, I went ahead, and merged the proposed change to trunk.
This means that the initial empty commit is no longer created by
surprise, but it's only a change of the default behavior: When
specifying
On Thu, May 8, 2014 at 8:43 AM, Gerald Gutierrez gerald.gutier...@gmail.com
wrote:
I stopped using Dropbox and started syncing to a private remote server. I
use cron to do a commit sync every hour, and fossil is run from a bash
script via cron. It seems that after a couple of successful
On Thu, May 8, 2014 at 12:29 PM, Jan Nijtmans jan.nijtm...@gmail.comwrote:
tests to assure that. Actually, fossil cannot do very much when dealing
with an empty repository. Merging??? against what branch
It's funny you say that because in libfossil i've had to go back and
reexamine my 0
With today's version of Fossil, I can't add anything to any
freshly-created repositories.
andy|slack|14:25|0|~/foo
$ f version
This is fossil version 1.29 [3ef59c357c] 2014-05-08 10:25:32 UTC
andy|slack|14:23|0|~
$ mkdir foo
andy|slack|14:23|0|~
$ cd foo
andy|slack|14:23|0|~/foo
$ f new
On Thu, May 8, 2014 at 9:26 PM, Andy Goth andrew.m.g...@gmail.com wrote:
With today's version of Fossil, I can't add anything to any
freshly-created repositories.
andy|slack|14:25|0|~/foo
May i say: that's a a pretty crazy prompt you have there!
$ f version
This is fossil version 1.29
On Thu, May 8, 2014 at 9:40 PM, Stephan Beal sgb...@googlemail.com wrote:
Confirmed:
[stephan@host:~/cvs/fossil/X/x]$ f com -m test
Seems to be caused by an ignored return value check which assumes true.
Should have a fix soon.
--
- stephan beal
http://wanderinghorse.net/home/stephan/
On 5/8/2014 2:40 PM, Stephan Beal wrote:
On Thu, May 8, 2014 at 9:26 PM, Andy Goth wrote:
andy|slack|14:25|0|~/foo
May i say: that's a a pretty crazy prompt you have there!
Username, hostname, time, background job count, current directory,
(newline), dollar sign or pound sign depending on
On Thu, May 8, 2014 at 9:46 PM, Andy Goth andrew.m.g...@gmail.com wrote:
Looking into it now, but suspect that Jan or Andy B might have a more
immediate suspicion, seeing as they've been around that code lately.
I think [3ef59c357c] is the culprit. In fact, the reason I made a new
On Thu, May 8, 2014 at 9:52 PM, Stephan Beal sgb...@googlemail.com wrote:
On Thu, May 8, 2014 at 9:46 PM, Andy Goth andrew.m.g...@gmail.com wrote:
Looking into it now, but suspect that Jan or Andy B might have a more
immediate suspicion, seeing as they've been around that code lately.
I
On Thu, May 8, 2014 at 9:57 PM, Stephan Beal sgb...@googlemail.com wrote:
Going back a version does indeed fix it. i'll roll back that commit, as
soon as i figure out what the proper approach is to rolling back a commit.
(Suggestions welcomed ;)
i always forget about move to new branch...
On Wed, May 7, 2014 at 12:59 AM, Andy Bradford
amb-sendok-1402034378.gfecjnjggaibliman...@bradfords.org wrote:
Thus said Rich Neswold on Wed, 16 Apr 2014 15:40:23 -0500:
It would be nice if fossil would break the pull into smaller
transactions which contain valid timeline commits
I restrained myself in the previous discussion that ended up being about
the initial empty commit, but now I feel compelled: the rational,
discussion, and decision to remove the initial empty commit were pretty
poor, IMO. I don't want to belabor the point, so I'll leave it at that.
Happy to
Thus said Rich Neswold on Thu, 08 May 2014 15:18:43 -0500:
I was thinking of attacking the problem a little higher up (since I'm
way too nervous touching the low-level stuff):
So did I initially, though my first thought was simply to have autosync
try multiple times when failing (in the
On 2014-05-08 16:18, Rich Neswold wrote:
On Wed, May 7, 2014 at 12:59 AM, Andy Bradford
amb-sendok-1402034378.gfecjnjggaibliman...@bradfords.org wrote:
Thus said Rich Neswold on Wed, 16 Apr 2014 15:40:23 -0500:
It would be nice if fossil would break the pull into smaller
transactions
Thus said Doug Franklin on Thu, 08 May 2014 23:00:03 -0400:
Does SQLite support nested transactions? If so, that would seem to be
worth considering.
It does appear to support them:
https://www.sqlite.org/lang_transaction.html
Andy
--
TAI64 timestamp: 4000536c46e4
On Thu, May 8, 2014 at 10:08 PM, Andy Bradford amb-fos...@bradfords.org wrote:
Thus said Doug Franklin on Thu, 08 May 2014 23:00:03 -0400:
Does SQLite support nested transactions? If so, that would seem to be
worth considering.
It does appear to support them:
18 matches
Mail list logo
