yahns Ruby server user/dev discussion
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: yahns-public@yhbt.net
Subject: [PATCH] update documentation to reflect public-inbox/list
Date: Fri, 9 May 2014 00:37:11 +0000	[thread overview]
Message-ID: <20140509003711.GA12757@dcvr.yhbt.net> (raw)

Rubyforge is going away on May 15, so update our docs for it.
 Documentation/yahns-rackup.txt |  4 ++--
 Documentation/yahns.txt        |  2 +-
 HACKING                        |  4 ++--
 README                         | 12 +++++++-----
 4 files changed, 12 insertions(+), 10 deletions(-)

diff --git a/Documentation/yahns-rackup.txt b/Documentation/yahns-rackup.txt
index 269d013..2d2f420 100644
--- a/Documentation/yahns-rackup.txt
+++ b/Documentation/yahns-rackup.txt
@@ -132,7 +132,7 @@ See rackup documentation for more details.
-All feedback welcome via plain-text mail to <yahns-public@rubyforge.org>\
+All feedback welcome via plain-text mail to <yahns-public@yhbt.net>\
 No subscription is necessary to post to the mailing list.
@@ -148,5 +148,5 @@ yahns(1), yahns_config(5)
 * [Rack RDoc][1]
 * [Rackup HowTo][2]
-[1]: http://rack.rubyforge.org/doc/
+[1]: http://rdoc.info/gems/r#/gems/rack/frames
 [2]: http://wiki.github.com/rack/rack/tutorial-rackup-howto
diff --git a/Documentation/yahns.txt b/Documentation/yahns.txt
index 362851f..598104f 100644
--- a/Documentation/yahns.txt
+++ b/Documentation/yahns.txt
@@ -55,7 +55,7 @@ See yahns_config(5) for documentation on the configuration file format.
-All feedback welcome via plain-text mail to <yahns-public@rubyforge.org>\
+All feedback welcome via plain-text mail to <yahns-public@yhbt.net>\
 No subscription is necessary to post to the mailing list.
diff --git a/HACKING b/HACKING
index 99cd3c3..bb96e2d 100644
@@ -46,10 +46,10 @@ contact
 We use git(7) and develop yahns on a public mailing list like git
 developers do.  Please send patches via git-send-email(1) to the public
-mailing list at <yahns-public@rubyforge.org>.  Pull requests should be
+mailing list at <yahns-public@yhbt.net>.  Pull requests should be
 formatted using git-request-pull(1).
-Mailing list archives: http://rubyforge.org/pipermail/yahns-public/
+Mailing list archives: http://yhbt.net/yahns-public/
 No subscription is necessary to post to the mailing list.
 Please remember to Cc: all recipients.
diff --git a/README b/README
index 677c97d..1d7ed8f 100644
--- a/README
+++ b/README
@@ -56,17 +56,19 @@ Contact
 We are happy to see feedback of all types via plain-text email.
 Please send comments, user/dev discussion, patches, bug reports,
-and pull requests to the public mailing list at:
+and pull requests to the public inbox/mailing list at:
-	yahns-public@rubyforge.org
+	yahns-public@yhbt.net
 No subscription is necessary to post.  Please Cc: all recipients as
 subscription is not necessary.
-You may subscribe by sending a request to:
+You may subscribe by sending an email to:
-	yahns-public-request@rubyforge.org
-	with the Subject line: "subscribe"
+	yahns-public+subscribe@yhbt.net
+You may also subscribe to the public-inbox at git://yhbt.net/yahns-public
+using ssoma <http://ssoma.public-inbox.org/>
 This README is our homepage, we would rather be working on HTTP servers
 all day than worrying about the next browser vulnerability because
Eric Wong

                 reply	other threads:[~2014-05-09  0:37 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:

  List information: https://yhbt.net/yahns/README

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

  git send-email \
    --in-reply-to=20140509003711.GA12757@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=yahns-public@yhbt.net \


* 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


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).