Richard Hipp writes:
> Thanks everybody for letting me know that the SSL cert for SQLite and
> Fossil has expired. We are working the problem now. It is OK to stop
> sending me emails about it.
The SSL cert is updated now, thanks. But you removed the
intermediate certs, so users can't (easily
2015-04-13 6:31 GMT+02:00 Andy Bradford :
> It's not yet merged to trunk, but I have borrowed from Jan's work and
> merged into the sync-forkwarn branch for what I think will provide a
> better experience (e.g. almost no false positives).
>
> I say almost none, because it's possible that i
On 4/13/15, Volker Braun wrote:
> Richard Hipp writes:
>> Thanks everybody for letting me know that the SSL cert for SQLite and
>> Fossil has expired. We are working the problem now. It is OK to stop
>> sending me emails about it.
>
> The SSL cert is updated now, thanks. But you removed the
> i
On Fri, Apr 10, 2015 at 2:16 PM, Matt Welland
wrote:
> I myself prefer not to see additional info like this that can be derived
> from querying the db added to the timeline. I'm keen to see the work that
> Andy and Jan have done make it into the trunk and will test it ASAP.
>
There is a differen
Thus said Jan Nijtmans on Mon, 13 Apr 2015 10:59:38 +0200:
> - I'm not sure if I want to be reminded when someone else causes a
> fork on a branch I'm not working on. But if there is such a desire
> with other people, I'm not principally against it.
I asked a question a few days ag
Does fork notification really warrant another setting? If there is a fork
on some other branch either fix by merging it or rename one of the legs.
There is no sensible need for a fork to exist in a timeline that I can
think of. Forks are rare in most repos (the intensely busy repos I deal
with seem
On Mon, Apr 13, 2015 at 1:59 AM, Jan Nijtmans
wrote:
> 2015-04-13 6:31 GMT+02:00 Andy Bradford :
>
>> It's not yet merged to trunk, but I have borrowed from Jan's work and
>> merged into the sync-forkwarn branch for what I think will provide a
>> better experience (e.g. almost no false pos
Thus said Matt Welland on Mon, 13 Apr 2015 15:57:53 -0700:
> Does fork notification really warrant another setting?
Generally, I would prefer to avoid another setting, but wanted to make
sure.
> Forks are rare in most repos (the intensely busy repos I deal with
> seem to be the exception).
Thus said Jan Nijtmans on Mon, 13 Apr 2015 10:59:38 +0200:
> I'll do more testing on the "sync-forkwarn".
Thanks. One thing to note is that I extended the function
fossil_find_nearest_fork to be able to work without checking the vmerge
table which is only available for a reposit
Hello,
recently I switched from Gnucash to Ledger to keep record of my our finances
and everything is under Fossil.
The dbstat of the repo looks as follows:
repository-size: 428815360 bytes (428.8MB)
artifact-count:7731 (stored as 5556 full text and 2175 delta blobs)
artifact-sizes:988
10 matches
Mail list logo
