On Thu, May 8, 2014 at 10:08 PM, Andy Bradford 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:
>
> https://www.sqlite.org/lang_transaction.html
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 2014-05-08 16:18, Rich Neswold wrote:
On Wed, May 7, 2014 at 12:59 AM, Andy Bradford
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 so, if there's
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 Thu, May 8, 2014 at 10:17 AM, Stephan Beal wrote:
> I've seen references to fossil hanging before (but can't find it now). Is
>> this a known issue?
>>
>
> You're not by chance on Solaris, are you? That's the only platform i've
> see which likes to occasionally hang network traffic. (Long stor
Thus said Andy Goth on Thu, 08 May 2014 14:26:14 -0500:
> andy|slack|14:24|0|~/foo
> $ f commit -m test
> New_Version: 3a4aff36993d288a6dfb7b5c968c3af613c25547
> ERROR: [file] is 6 bytes on disk but 0 in the repository
> NOTICE: Repository version of [file] stored in [file-22ef63d951e2b17d]
> work
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 disc
On Wed, May 7, 2014 at 12:59 AM, Andy Bradford
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 so, if there's a
>> database timeout, the next tim
On Thu, May 8, 2014 at 9:57 PM, Stephan Beal 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..."
Richard just move
On Thu, May 8, 2014 at 9:52 PM, Stephan Beal wrote:
> On Thu, May 8, 2014 at 9:46 PM, Andy Goth 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
On Thu, May 8, 2014 at 9:46 PM, Andy Goth 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
> repository was to test t
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 U
On Thu, May 8, 2014 at 9:40 PM, Stephan Beal 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/
http://gplus.to/s
On Thu, May 8, 2014 at 9:26 PM, Andy Goth 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 [3ef59c357c] 2014-
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 foo.f
On Thu, May 8, 2014 at 12:29 PM, Jan Nijtmans wrote:
> 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 semantics, and let th
On Thu, May 8, 2014 at 8:43 AM, Gerald Gutierrez 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 runs, the
> fossil process s
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 "--date
2014-05-01 12:28 GMT+02:00 Stephan Beal :
> 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 an RID>0 and might
19 matches
Mail list logo
