caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: ygrek <ygrekheretix@gmail.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] [ANN] ocurl forked and 0.5.4 released
Date: Wed, 6 Feb 2013 00:33:42 +0200	[thread overview]
Message-ID: <20130206003342.a06e22b3c6639fb96531cd4f@gmail.com> (raw)
In-Reply-To: <510CEA1B.2070809@vb.fdn.fr>

On Sat, 02 Feb 2013 11:27:39 +0100
"Vincent B." <vb@vb.fdn.fr> wrote:

> 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.

Ack.
Thanks for clearing this up and getting to original author.
As per response by Lars this issue is now settled, for great good :)

-- 
 ygrek
 http://ygrek.org.ua

      parent reply	other threads:[~2013-02-05 22:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-30 23:03 ygrek
2013-01-31  9:21 ` Goswin von Brederlow
2013-02-02 10:27   ` Vincent B.
2013-02-04 11:06     ` Goswin von Brederlow
2013-02-05 22:33     ` ygrek [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=20130206003342.a06e22b3c6639fb96531cd4f@gmail.com \
    --to=ygrekheretix@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).