ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Philipp Gesang <phg@phi-gamma.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: git mirror [was: Re: Sourcemirror at gitorious is closing down, where to find it then?]
Date: Wed, 10 Jun 2015 00:07:17 +0200	[thread overview]
Message-ID: <20150609220714.GA11363@acheron> (raw)
In-Reply-To: <54FF2203.1040500@wxs.nl>


[-- Attachment #1.1: Type: text/plain, Size: 1658 bytes --]

Hey guys,

sorry for the late reply, this kind of got buried in my inbox so
only now I noticed the thread on the ML archives. Nevertheless:

···<date: 2015-03-10, Tuesday>···<from: Hans Hagen>···

> On 3/10/2015 5:39 PM, Mojca Miklavec wrote:
> > On Tue, Mar 10, 2015 at 4:56 PM, Norbert Melzer wrote:
> > - BitBucket used to be hg-only. I see no reason not to have a mirror
> > there as well (but I don't see any particular need for yet another
> > mirror either). If there are enough people who think that having yet
> > another mirror on BitBucket as well would be useful for whatever
> > reason, let me know.
> 
> indeed, a volunteer using that could also keep it up to date

My Git mirror on Bitbucket still keeps the repo in sync:

      https://bitbucket.org/phg/context-mirror/

Originally based on the Gitorious repo, it has been tracking
Context development for a year or so by now. As a feature over
Marius’s approach it keeps the beta and current in separate
branches and will also pull from the Garden just in case:

      https://bitbucket.org/phg/context-mirror/branches

I’ve been relying on the mirror as my primary source for change
notifications and diffs of the Context source for some time now.

For those interested in setting up a mirror themselves I can
provide the source of the bot. There’s some docs but I took some
shortcuts like hard-coding paths and SSH stuff so it might take
a little effort to get it up to full speed. OTOH doesn’t appear
to be unreliable and should continue working as long as the
Pragma website can be scraped in the same fashion ;)

Best,
Philipp


[-- Attachment #1.2: Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2015-06-09 22:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10 15:56 Sourcemirror at gitorious is closing down, where to find it then? Norbert Melzer
2015-03-10 16:39 ` Mojca Miklavec
2015-03-10 16:55   ` Hans Hagen
2015-06-09 22:07     ` Philipp Gesang [this message]
2015-06-10  9:07       ` git mirror [was: Re: Sourcemirror at gitorious is closing down, where to find it then?] Hans Hagen
2015-03-10 16:57 ` Sourcemirror at gitorious is closing down, where to find it then? Pablo Rodriguez

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=20150609220714.GA11363@acheron \
    --to=phg@phi-gamma.net \
    --cc=ntg-context@ntg.nl \
    /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).