Will do unless someone beats me to the commit :)
On 11 Nov 2015 1:53 a.m., "Thomas Gazagnaire" wrote:
> > (Aside: Why did we decide we needed all past images in the current
> > checkout of the deployment repos anyway?)
>
> just delete the old images. We certainly don't need to keep all of them in
> 2. I'd love to be able to get at the configuration options as data, in
> an ideal world JSON, probably something like a generated JSON schema
> (http://json-schema.org/)
>
> My rationale for the last part is integration with other tools.
> Personally I'd love to be able to autogenerate Puppet ty
> (Aside: Why did we decide we needed all past images in the current
> checkout of the deployment repos anyway?)
just delete the old images. We certainly don't need to keep all of them in the
current checkout.
___
MirageOS-devel mailing list
MirageOS
Hi folks,
The next MirageOS call will take place on Wednesday afternoon at 4pm GMT and is
open to all.
We'll continue using Jitsi [1] and I’ll post the link shortly before the call,
both here and also in the IRC channel (#mirage on freenode) [hint: it’ll be the
same as last time]
The agenda i
On 10 November 2015 at 16:49, Rupert Horlick wrote:
> I'm implementing this for a Part II project, so I've decided to go ahead and
> implement my own simple FS for BLOCK, rather than using IRMIN.
>
> However, I'm coming across the difficulties that Dave mentioned,
Simple and in-memory is (surely!
I'm implementing this for a Part II project, so I've decided to go ahead
and implement my own simple FS for BLOCK, rather than using IRMIN.
However, I'm coming across the difficulties that Dave mentioned, so I'm
reading up on B-trees as we speak. I may well end up writing a simple
B-tree library,
Hi Luis (+CC OPAM/Mirage lists as FYI),
I've uploaded OCaml 4.02.3 and OPAM 1.2.2 PPA builds for Wily to Launchpad,
where they're building in the experimental repository. Once that's completed
(which takes a while due to the ARM builds), I will move them over to the
stable PPAs.
Note that OPA
On Mon, Nov 9, 2015 at 3:46 PM, Thomas Leonard wrote:
> Hi Rupert,
>
> The main thing is to implement Irmin's AO signature:
>
>
> https://github.com/mirage/irmin/blob/4b5d3117e4cc1ecff4a83cc508da59006423/lib/irmin.mli#L360
>
> i.e. given a block of data, write it to disk and return its hash.
We're looking into the OCaml cohttp library. We want to build a simple
REST-server based on top of it. We'd be using it to transfer large quantities
of data. The cohttp library in this case will need to fall back to chunked
transfer.
We dug a bit around in the source code and we suspect tha
Hi;
It has been noticed that one of the issues with the current site
deployment process (push Travis built Xen VM images into a GitHub
repo, run cron jobs to periodically pull that repo to the deployment
machine, have a post-merge.hook that deploys when the deployment repo
is determined to have be
10 matches
Mail list logo
