caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Lars Nilsson <chamaeleon@gmail.com>
To: "Vincent B." <vb@vb.fdn.fr>
Cc: caml-list@inria.fr
Subject: Re: Re: [Caml-list] [ANN] ocurl forked and 0.5.4 released
Date: Sat, 2 Feb 2013 15:22:11 -0500	[thread overview]
Message-ID: <CABqmBnGguMXhDTMhRFb9TzXpsGNv2affXh6YSt18+ptEKWuXow@mail.gmail.com> (raw)
In-Reply-To: <510D7014.7000001@vb.fdn.fr>

Reply vs Reply All miss by me. Sorry, Vincent.

Lars Nilsson

On Sat, Feb 2, 2013 at 2:59 PM, Vincent B. <vb@vb.fdn.fr> wrote:
> -------- Original Message --------
> Subject: Re: [Caml-list] [ANN] ocurl forked and 0.5.4 released
> Date: Sat, 2 Feb 2013 14:29:58 -0500
> From: Lars Nilsson <chamaeleon@gmail.com>
> To: Vincent B. <vb@vb.fdn.fr>
>
> On Sat, Feb 2, 2013 at 5:27 AM, Vincent B. <vb@vb.fdn.fr> wrote:
>>
>>
>> On 31/01/2013 10:21, Goswin von Brederlow wrote:
>>>
>>>
>>> Can you tell us why you need to fork ocurl? Why not continue the original
>>> project?
>>>
>>> And if you must fork then please change the name so the two don't get
>>> confused.
>>>
>>> MfG
>>>         Goswin
>>
>>
>>
>> Hi,
>>
>> This fork started as I (on behalf of the OPAM team) asked for a fork of
>> ocurl to include in OPAM since the original ocurl has not been updated for a
>> long time, and is not compiling anymore out of the box, at least on recent
>> versions of OCaml. Moreover as ygrek said, his version accumulates lots of
>> bugfixes meant to be integrated into the official branch for a long time
>> already, that could not make it because the original author did not answer
>> at all.
>>
>> The need of a fork arises from what is mentionned before, mostly the
>> original author being unreachable and the changes accumulating too much to
>> be kept as separate patches.
>>
>> As for changing the name, I would personally not do it since it is a
>> rightful continuation of the ocurl project (and is backward compatible). I’m
>> suggesting to wait for the original ocurl author to reappear to see if we
>> can finally merge the changes.
>>
>> Cheers,
>>
>> Vincent
>
>
> I have no problem with this fork, or the name remaining the same. I
> have not used OCaml in a long time and people more active than me
> probably are better at taking care of it at this point.
>
> Lars Nilsson
>
>
>
>
> --
> 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:[~2013-02-02 20:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CABqmBnEbe6KovqYx+W_wG76R7w9bkHRiWMrJrGenzuESfPuq1Q@mail.gmail.com>
2013-02-02 19:59 ` Fwd: " Vincent B.
2013-02-02 20:22   ` Lars Nilsson [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=CABqmBnGguMXhDTMhRFb9TzXpsGNv2affXh6YSt18+ptEKWuXow@mail.gmail.com \
    --to=chamaeleon@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=vb@vb.fdn.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).