user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: ruby-core@ruby-lang.org, ruby-dev@ruby-lang.org
Cc: meta@public-inbox.org
Subject: ruby-dev (Japanese) list archive mirror
Date: Sun, 2 Jul 2017 21:36:57 +0000	[thread overview]
Message-ID: <20170702213657.GA5312@dcvr> (raw)

Hello, I have enabled https://public-inbox.org/ruby-dev/ for
mirroring the (mostly) Japanese dev list.  Xapian search does
not seem prepared for Japanese, but of course English-based
source code remains searchable(*).

NNTP readers can use:

        nntp://news.public-inbox.org/inbox.comp.lang.ruby.dev

Tor .onion endpoints are also available:

	nntp://ou63pmih66umazou.onion/inbox.comp.lang.ruby.dev
	http://ou63pmih66umazou.onion/ruby-dev/


I made a similar announcement for ruby-core:
  [ruby-core:81743] https://public-inbox.org/ruby-core/20170623032722.GA8124@dcvr/

Likewise, the "dev:#{number}" search works when
referring to [ruby-dev:#{number}]:

	https://public-inbox.org/ruby-dev/?q=dev:12345

You can also clone all the messages (around 80 MB):

	git clone --mirror https://public-inbox.org/ruby-dev
	(and periodically run "git fetch" to update)

And the AGPL-3.0+ source code (sorry, it's Perl5):

	git clone https://public-inbox.org/public-inbox

And hack+run it yourself, too.

ruby-talk seems too big for me to archive, at the moment :<


(*) maybe I will try Rroonga/Groonga in a Ruby port of
    public-inbox in the future :)

                 reply	other threads:[~2017-07-02 21:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170702213657.GA5312@dcvr \
    --to=normalperson@yhbt.net \
    --cc=meta@public-inbox.org \
    --cc=ruby-core@ruby-lang.org \
    --cc=ruby-dev@ruby-lang.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).