From: Jeremie Dimino <jdimino@janestreet.com>
To: ocaml-core@googlegroups.com
Cc: caml-list@inria.fr
Subject: [Caml-list] Re: [ANN] Core Suite 109.14.00 released + custom_printf
Date: Wed, 20 Mar 2013 09:45:17 +0000 [thread overview]
Message-ID: <CANhEzE7kEzXOL9ua4v9zZeDhgbuO9rJSRLcHdWO3qrBt7diQtA@mail.gmail.com> (raw)
In-Reply-To: <d1f05922-b604-413d-a3b5-731256472524@googlegroups.com>
On Wed, Mar 20, 2013 at 9:34 AM, Stanislav Artemkin <artemkin@gmail.com> wrote:
> Bitbucket doesn't contain latest changes. Do I correctly understand that
> Github is a main source?
It is just that hg-git stopped working and I haven't investigated it yet.
> What is the strategy of updating Bitbucket repos?
I import the changes from the git repos and push them to Bitbucket.
Jeremie
next prev parent reply other threads:[~2013-03-20 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 14:35 [Caml-list] " Jeremie Dimino
2013-03-20 9:34 ` [Caml-list] " Stanislav Artemkin
2013-03-20 9:45 ` Jeremie Dimino [this message]
2013-03-20 10:19 ` Jeremie Dimino
[not found] ` <99faa97e-6bb9-4405-99cb-e2e1939396f6@googlegroups.com>
2013-05-17 9:17 ` Jeremie Dimino
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=CANhEzE7kEzXOL9ua4v9zZeDhgbuO9rJSRLcHdWO3qrBt7diQtA@mail.gmail.com \
--to=jdimino@janestreet.com \
--cc=caml-list@inria.fr \
--cc=ocaml-core@googlegroups.com \
/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