caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Dario Teixeira <darioteixeira@yahoo.com>
To: Anil Madhavapeddy <anil@recoil.org>
Cc: OCaml mailing-list <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml Forge and Github
Date: Mon, 30 Sep 2013 04:18:26 -0700 (PDT)	[thread overview]
Message-ID: <1380539906.12125.YahooMailNeo@web120406.mail.ne1.yahoo.com> (raw)
In-Reply-To: <F2A1FDBB-6C21-49C3-B956-A5460D17FF5E@recoil.org>

Hi Anil,

> (...)

> You may be able to handle the Forge interaction through that mechanism, for
> instance by doing an SVN commit from the Git push hook. I'm experimenting
> with building ocamldoc for every package and pushing it to the gh-pages
> branch (so that it's published on GitHub pages automatically on every push).

Even if I decided to keep a repo on the Forge, I would migrate it to Git anyway.
Not only wouldn't I have to worry about possible issues in the Git -> SVN bridge,
it would be my little contribution to burying SVN...


> Incidentally, the scripts that convert the OCaml SVN to Git are available:
> https://github.com/ocaml/ocaml.org-scripts/tree/master/vcs-sync/svn-ocaml
> 
> They are a bit smarter than the average SVN->Git convertor and create real
> git branches for SVN tags.  This may help you if you wish to migrate from
> SVN to Git (even if the Forge supports git, it probably requires this 
> conversion process too).

I was just looking into tools to ease that process -- thanks!

Best regards,
Dario Teixeira

  reply	other threads:[~2013-09-30 11:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-29 17:13 Dario Teixeira
2013-09-29 21:53 ` Fabrice Le Fessant
2013-09-30  0:44   ` Sylvain Le Gall
2013-09-30 11:48     ` Dario Teixeira
2013-09-30 12:39       ` Sylvain Le Gall
2013-09-30 10:36   ` Dario Teixeira
2013-09-30  0:43 ` Anil Madhavapeddy
2013-09-30 11:18   ` Dario Teixeira [this message]
2013-09-30 10:44 ` Paolo Donadeo
2013-09-30 10:48   ` Anil Madhavapeddy
2013-09-30 14:20     ` Sylvain Le Gall

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=1380539906.12125.YahooMailNeo@web120406.mail.ne1.yahoo.com \
    --to=darioteixeira@yahoo.com \
    --cc=anil@recoil.org \
    --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).