caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Pierre-Étienne Meunier" <pierre-etienne.meunier@aalto.fi>
To: <caml-list@inria.fr>
Subject: [Caml-list] Pijul 0.1
Date: Thu, 1 Oct 2015 19:10:49 +0300	[thread overview]
Message-ID: <20151001161049.GC22139@aalto.fi> (raw)

Dear Caml list,

Florend Becker and myself are honoured to present version 0.1 of
Pijul. Pijul is a draft of a prototype of an implementation of Samuel
Mimram and Cinzia Di Giusto's theory of patches.

Where can I learn more? Where can I find this pijul?
====================================================

Pijul's homepage is http://pijul.org ; its sources are found at "darcs
get http://pijul.org". Both are a bit rough at the moment, but should
improve rapidly, maybe with your help…

There is a mailing list (pijul@pijul.org), and an irc channel should
be setup Real Soon Now™.

Currently, pijul has a preliminary implementation of darcs' basic
commands.

What is a pijul, and how do I pronounce it?
===========================================

A pijul is a south american bird (Crotophaga sulcirostris), a relative
of the cuckoo. In contrast with its parasitic cousin, the pijul lays
her eggs in a communal nest, where they are incubated by the whole
community.

Pijul is thus pronounced as in spanish, IPA [pijul], or aproximately
pee-hhOOl (the hh is the sound at the end of scottish 'loch').

What is the Di Giusto-Mimram Patch Theory?
==========================================

Pijul's patch theory originates in this paper:
http://arxiv.org/abs/1311.3903 .

Darcs' patch theory is centered around patches, with two primitive
operations, /commutation/ and /inversion/. Compared to this, pijul's
theory revolves around files (i.e., states of the working directory at a
given point in time) as well as patches, with a /merge/ operation
between patches. In contrast with git, this merge operation is
well-defined and has all expected properties: in technical terms, it is
a /pushout/ in a category where files are the objects, and patches are
the arrows. As a consequence of this, to ensure all diverging pairs of
patches have a merge, the set of files is extended to contain normal
files as well as /files in a conflicted state/. These conflicted files
are /rendered/ into the working directory by pijul as files with
conflict markings.

Thanks to this categorical construction, the Pijul version of most
algorithms used in darcs is conceptually simple and efficient.

What colour should the bikeshed be?
===================================

Blanquiceleste


Cheers,
Pierre-Étienne Meunier


             reply	other threads:[~2015-10-01 16:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-01 16:10 Pierre-Étienne Meunier [this message]
2015-10-25 21:00 ` yoann padioleau
2015-10-26  5:19   ` Pierre-Étienne Meunier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151001161049.GC22139@aalto.fi \
    --to=pierre-etienne.meunier@aalto.fi \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).