[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MirageOS-devel] Changes in Irmin 0.10.0



On 11 January 2016 at 15:07, M. O. <meta@xxxxxxx> wrote:
> I understand. Irmin.unwatch appears to be Unbounded when building (while
> Irmin.watch_key works). Doesn't unwatch need to be exposed in module BC?

I don't think so. The documentation says:

(** [watch_branches t f] calls [f] every time a branch is added,
removed or updated in the local store. Return a function to remove the
handler. *)

> On 10 January 2016 at 16:50, M. O. <meta@xxxxxxx> wrote:
>> Thanks, and how to unwatch a key that is under watch by I.watch_key?
>
> The Irmin API is documented in irmin.mli, e.g.
>
> https://github.com/mirage/irmin/blob/master/lib/irmin.mli#L533
>
>
>>> Hi,
>>>
>>> Questions regarding changes in Irmin 0.10.0:
>>>
>>> 1- Is there any equivalence for "Irmin.watch_tags" in the previous
>>> releases?
>>
>> Irmin.Repo.watch_branches
>>
>>> 2- This is somehow related to the first question, that is how to create a
>>> store similar to "Store.of_head config task head" (for instance, from the
>>> heads that watch_tag sends to the callback function) in the older
>>> versions.
>>
>> of_head is now of_commit_id.
>>
>
>
>
> --
> Dr Thomas Leonard http://roscidus.com/blog/
> GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA



-- 
Dr Thomas Leonard        http://roscidus.com/blog/
GPG: DA98 25AE CAD0 8975 7CDA  BD8E 0713 3F96 CA74 D8BA

_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.