caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Anil Madhavapeddy <anil@recoil.org>
To: Goswin von Brederlow <goswin-v-b@web.de>
Cc: "Richard W.M. Jones" <rich@annexia.org>, caml-list@inria.fr
Subject: Re: [Caml-list] Trivial compiler patches
Date: Thu, 27 Mar 2014 11:22:05 +0000	[thread overview]
Message-ID: <ABC1F72E-61A4-40FE-8163-A0B21B3FF2EA@recoil.org> (raw)
In-Reply-To: <20140327093420.GA19960@frosties>

On 27 Mar 2014, at 09:34, Goswin von Brederlow <goswin-v-b@web.de> wrote:

>> 
>> - github is closed source
> 
> I don't mind. It is free as in beer, it works and it doesn't poison
> your project (no lock in). You can always just use plain git at any
> time, which is free.

There's a significant amount of metadata that isn't track in Git.
Issues, pull requests, releases, comments, descriptions are all
available via the API, but not in Git.  Thomas Gazagnaire started
a CLI that dumps that information into a local git repository using
his ocaml-git implementation, but it's not quite complete yet. Do
get in touch if anyone's interested in helping finishing that effort
off to provide a GitHub export to a more neutral format...

-anil

  reply	other threads:[~2014-03-27 11:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21 22:28 Richard W.M. Jones
2014-03-22  0:46 ` Jacques Garrigue
2014-03-22  7:15   ` Richard W.M. Jones
2014-03-22  8:28     ` Gabriel Scherer
2014-03-25 15:49       ` Goswin von Brederlow
2014-03-25 16:01         ` Daniel Bünzli
2014-03-25 16:16         ` Richard W.M. Jones
2014-03-25 16:29           ` Anil Madhavapeddy
2014-03-27  9:34           ` Goswin von Brederlow
2014-03-27 11:22             ` Anil Madhavapeddy [this message]
2014-03-27 11:28               ` Thomas Gazagnaire
2014-03-27 12:23             ` François Bobot

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=ABC1F72E-61A4-40FE-8163-A0B21B3FF2EA@recoil.org \
    --to=anil@recoil.org \
    --cc=caml-list@inria.fr \
    --cc=goswin-v-b@web.de \
    --cc=rich@annexia.org \
    /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).