Re: [fossil-users] Merge tracking tests in a blog entry, some questions

gt;> that one branch has been merged with other without actually changing > >> any of the code? I don't recall ever having had a need for such a > thing? Can you suggest a scenario where it might be useful? > There are plenty of useful scenarios, but the biggest is 'maintained di

Re: [fossil-users] Merge tracking tests in a blog entry, some questions

Thanks Stephen & Richard. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Merge tracking tests in a blog entry, some questions

> On Sat, Jun 18, 2016 at 1:21 PM, Paul Hammant <p...@hammant.org> wrote: > >> Curiosities: >> >>- Having a database name rather than just a .git or .svn folder >>convention >>- The 'open' step. >> >> Fossil and SVN are more similar

[fossil-users] Merge tracking tests in a blog entry, some questions

Hi there. I did a blog entry on Fossil, and how it is able to handle a cherry-pick merge scenario that breaks subversion: http://paulhammant.com/2016/06/18/subversion-merge-limitations-not-in-fossil/ Learning curve for Fossil - about an hour. Curiosities: - Having a database name rather

[fossil-users] Bitrot defense?

Bitrot - http://arstechnica.com/information-technology/2014/01/bitrot-and-atomic-cows-inside-next-gen-filesystems/ - data in SSD or HD being corrupted by (say) nutrinos over time. See also a guy/gal lamenting their corrupted photo collection - https://blog.barthe.ph/2014/06/10/hfs-plus-bit-rot/

Re: [fossil-users] fossil-scm as an SQLite db with schema/data revision control

Adam, > So basically, this could be a distributed, multi-user database. > Each user would have a local copy (fast access) with their own branches > (write control) but there could be data sharing through merges. (This > probably sounds obvious to fossil users but think about it from the >

Re: [fossil-users] Bitrot defense?

he article so you > already know that... > >> On Tue, Jun 28, 2016 at 1:09 PM, Paul Hammant <p...@hammant.org> wrote: >> Bitrot - >> http://arstechnica.com/information-technology/2014/01/bitrot-and-atomic-cows-inside-next-gen-filesystems/ >> - data in SSD or HD

Re: [fossil-users] Bitrot defense?

> > > Fossil *could* be modified to self-repair. It has the info it needs to do > so. > > But then, why bother in a world where you have things like ZFS, which can > protect not only your Fossil repos, but also everything else you hold dear? > So say the's an old version of a PNG that's corrupt

Re: [fossil-users] Bitrot defense?

mail list). - Paul On Wed, Jul 6, 2016 at 6:14 AM, Kees Nuyt <k.n...@zonnet.nl> wrote: > [Default] On Wed, 6 Jul 2016 05:02:40 -0400, Paul Hammant > <p...@hammant.org> wrote: > > > ZFS, Btrfs could repair a Fossil database inflight, and without hiccup? > > Tell

Re: [fossil-users] Bitrot defense?

> Those filesystems don’t need to know Fossil’s internals at all. >Self-repair only requires checksums and redundancy. If one checksum doesn’t match the contents of the data being checksummed, another copy of the data is checked, and if its contents match the checksum, it is presumed to be the

Re: [fossil-users] Fossil as an app server?

Thanks Joe, thanks Stephen. Joe, Here's a "seatmap" app I made using CouchDB - http://paulhammant.com/2015/12/21/angular-and-svg-and-couchdb/. It works with CORS enabled. In the new Serverless era ( https://martinfowler.com/articles/serverless.html - Mike is a buddy and former colleague of

Re: [fossil-users] Fossil as an app server?

Are you sure there's not some no-frills way of getting at what used to be on Google code - e.g. https://code.google.com/archive/p/majesticuo/source/default/source ? On Thu, Mar 30, 2017 at 7:01 AM, ng0 <contact@cryptolab.net> wrote: > Paul Hammant transcribed 4.8K bytes: >

[fossil-users] Fossil as an app server?

Fossil being comfortable serving up HTML is well known. Could I serve up (say) an AngularJS app that spoke HTTP back to the Fossil server to effectively do CRUD operations on a JSON document at HEAD revision? I see that Fossil doesn't follow PUT/POST verbs*, but that doesn't really matter if the

Re: [fossil-users] Fossil as an app server?

Or maybe examples of curl commands that can demonstrate CRUD operations against a Fossil repo HTTP interface? ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] REST API and client for same

> > > I have little need for such a thing myself, so I’m just throwing this idea > out there for anyone who thinks it looks like a good itch to scratch. > I do have a need for this class of use. My thread "Fossil as an app server" (nearly a week ago on this list) is in the same direction.

Re: [fossil-users] REST API and client for same

on them, and commit them back as a set, atomically? - Paul - Paul On Tue, Apr 4, 2017 at 2:53 PM, Warren Young <war...@etr-usa.com> wrote: > On Apr 4, 2017, at 11:24 AM, Paul Hammant <p...@hammant.org> wrote: > > > > > I have little need for such a thing myself, so I’m just

Re: [fossil-users] REST API and client for same

OK, so I don't think there's any interest in this beyond me :-( On Wed, Apr 5, 2017 at 1:58 PM, Paul Hammant <p...@hammant.org> wrote: > I don't really need Fossil to become an application server. I just need > it to handle CRUD over HTTPS on specific resources, and have

Re: [fossil-users] TinyMCE for editing wiki pages

BSD codebases can use LGPL components/libs without fear of being in violation of license. On Wed, Jun 7, 2017 at 6:10 AM, Richard Hipp wrote: > On 6/7/17, Chris Rydalch wrote: > > I tried following the Cookbook page, but haven't had luck getting it to > >