kgio RubyGem user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <>
Subject: [PATCH 3/3] doc: move from to
Date: Wed, 25 Dec 2019 22:58:50 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

.org is being sold to extortionists and I couldn't afford
to pay the bill to renew either way.  So kick
it to and be prepared to change when extortionists
move onto the .net TLD...
 .olddoc.yml  | 10 +++++-----
 GNUmakefile  |  2 +-
 HACKING      |  4 ++--
 ISSUES       | 12 ++++++------
 README       |  6 +++---
 kgio.gemspec |  4 ++--
 6 files changed, 19 insertions(+), 19 deletions(-)

diff --git a/.olddoc.yml b/.olddoc.yml
index 2e9bb79..e89ecab 100644
--- a/.olddoc.yml
+++ b/.olddoc.yml
@@ -1,9 +1,9 @@
-git_url: git://
+git_url: git://
diff --git a/GNUmakefile b/GNUmakefile
index 02d08ba..be94594 100644
--- a/GNUmakefile
+++ b/GNUmakefile
@@ -1,4 +1,4 @@
 rfpackage := kgio
diff --git a/HACKING b/HACKING
index b94f25c..e124c33 100644
@@ -6,7 +6,7 @@ Please wrap documentation at 72 characters-per-line or less (long URLs
 are exempt) so it is comfortably readable from terminals.
 When referencing mailing list posts, use
-<tt>$MESSAGE_ID/</tt> if possible
+<tt>$MESSAGE_ID/</tt> if possible
 Message-ID remains searchable even if the archive becomes unavailable.
 === Code Compatibility
@@ -25,7 +25,7 @@ characters wide) and NOT the indentation style of Matz Ruby.
 Contributions are welcome in the form of patches, pull requests, code
 review, testing, documentation, user support or any other feedback.  The
-{kgio mailing list}[] is the
+{kgio mailing list}[] is the
 central coordination point for all user and developer feedback and bug
diff --git a/ISSUES b/ISSUES
index a5ed1d4..c26364f 100644
--- a/ISSUES
+++ b/ISSUES
@@ -1,9 +1,9 @@
 = Issues
-The kgio {mailing list}[] is the best
+The kgio {mailing list}[] is the best
 place to report bugs, submit patches and/or obtain support after you
-have searched the mailing list archives at
-and {documentation}[].
+have searched the mailing list archives at
+and {documentation}[].
 * Do not {top post}[] in replies
 * Quote only the relevant portions of the message you're replying to
@@ -20,10 +20,10 @@ guidelines for patch submission.
 == Mailing List Info
-* subscribe:
-* post:
+* subscribe:
+* post:
 == Mailing List Archives
 * nntp://
diff --git a/README b/README
index 4b1724f..0aedaf0 100644
--- a/README
+++ b/README
@@ -39,13 +39,13 @@ You may install it via
 You can get the latest source via git from the following locations
 (these versions may not be stable):
-  git://
+  git://
   git:// (mirror)
 You may browse the code from the web and download the latest snapshot
 tarballs here:
 * (gitweb)
 See the HACKING guide on how to contribute and build prerelease gems
@@ -55,7 +55,7 @@ from git.
 All feedback (bug reports, user/development dicussion, patches, pull
 requests) go to the mailing list/newsgroup.  See the ISSUES document for
-information on the {kgio mailing list}[]
+information on the {kgio mailing list}[]
 For the latest on kgio releases, you may check our NEWS page (and
 subscribe to our Atom feed).
diff --git a/kgio.gemspec b/kgio.gemspec
index de85c39..8c15bd3 100644
--- a/kgio.gemspec
+++ b/kgio.gemspec
@@ -4,7 +4,7 @@ manifest = File.readlines('.manifest').map! { |x| x.chomp! } do |s| = %q{kgio}
   s.version = ENV["VERSION"].dup
-  s.homepage = ''
+  s.homepage = ''
   s.authors = ['kgio hackers']
   s.description = <<EOF
 This is a legacy project, do not use it for new projects.  Ruby
@@ -12,7 +12,7 @@ This is a legacy project, do not use it for new projects.  Ruby
 non-blocking I/O methods for Ruby without raising exceptions on
- = %q{}
+ = %q{}
   s.extra_rdoc_files = IO.readlines('.document').map!(&:chomp!).keep_if do |f|

      parent reply	other threads:[~2019-12-25 22:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-25 22:43 -> Eric Wong
2019-12-25 22:58 ` [PATCH 1/3] build: remove olddoc from the gemspec Eric Wong
2019-12-25 22:58   ` [PATCH 2/3] doc: remove private email and outdated gmane archives Eric Wong
2019-12-25 22:58   ` Eric Wong [this message]

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:

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

  git send-email \ \ \ \

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