caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Pierre-Étienne Meunier" <pierre-etienne.meunier@aalto.fi>
To: yoann padioleau <aryx.padator@gmail.com>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Pijul 0.1
Date: Mon, 26 Oct 2015 07:19:59 +0200	[thread overview]
Message-ID: <20151026051959.GA3920@aalto.fi> (raw)
In-Reply-To: <F90CF834-C115-4FD5-8058-D12C9D803F5E@gmail.com>

This is not absolutely clear, we don't want to be held back by forward compatibility constraints too soon.
It can definitely handle large codebases, if we believe our benchmarks.

On Sun, Oct 25, 2015 at 02:00:59PM -0700, yoann padioleau wrote:
>Hi,
>
>When do you think pijul will be self-sustaining?
>Can it handle codebase like the linux kernel?
>
>> On Oct 1, 2015, at 9:10 AM, Pierre-Étienne Meunier <pierre-etienne.meunier@aalto.fi> wrote:
>>
>> Dear Caml list,
>>
>> Florent 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
>>
>>
>> --
>> Caml-list mailing list.  Subscription management and archives:
>> https://sympa.inria.fr/sympa/arc/caml-list
>> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
>> Bug reports: http://caml.inria.fr/bin/caml-bugs
>

      reply	other threads:[~2015-10-26  5:20 UTC|newest]

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

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=20151026051959.GA3920@aalto.fi \
    --to=pierre-etienne.meunier@aalto.fi \
    --cc=aryx.padator@gmail.com \
    --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).