user/dev discussion of public-inbox itself
 help / color / Atom feed
From: Eric Wong <>
Subject: [PATCH 5/5] spelling: favor `publicly' over `publically'
Date: Fri, 24 Jan 2020 22:09:33 +0000
Message-ID: <> (raw)
In-Reply-To: <>

While both can be correct, the former seems more common,
is shorter, and is also consistent with the spelling found
in the AGPL-3.0 text.
 Documentation/public-inbox-v2-format.pod | 2 +-
 TODO                                     | 2 +-
 lib/PublicInbox/             | 2 +-
 lib/PublicInbox/                  | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/Documentation/public-inbox-v2-format.pod b/Documentation/public-inbox-v2-format.pod
index 10c63090..0a391e1e 100644
--- a/Documentation/public-inbox-v2-format.pod
+++ b/Documentation/public-inbox-v2-format.pod
@@ -168,7 +168,7 @@ easier.  object_id and Message-ID are already known.
 =item object_id
 The blob identifier git uses (currently SHA-1).  No need to
-publically expose this outside of normal git ops (cloning) and
+publicly expose this outside of normal git ops (cloning) and
 there's no need to make this searchable.  As with v1 of
 public-inbox, this is stored as part of the Xapian document so
 expensive name lookups can be avoided for document retrieval.
diff --git a/TODO b/TODO
index 46c61f8e..a3b2b7cb 100644
--- a/TODO
+++ b/TODO
@@ -21,7 +21,7 @@ all need to be considered for everything we introduce)
 * HTTP and NNTP proxy support.  Allow us to be a frontend for
   firewalled off (or Tor-exclusive) instances.  The use case is
-  for offering a publically accessible IP with a cheap VPS,
+  for offering a publicly accessible IP with a cheap VPS,
   yet storing large amounts of data on computers without a
   public IP behind a home Internet connection.
diff --git a/lib/PublicInbox/ b/lib/PublicInbox/
index baad981d..06b4cdc4 100644
--- a/lib/PublicInbox/
+++ b/lib/PublicInbox/
@@ -5,7 +5,7 @@
 # searching inboxes for post-image blobs.
 # this emits a lot of debugging/tracing information which may be
-# publically viewed over HTTP(S).  Be careful not to expose
+# publicly viewed over HTTP(S).  Be careful not to expose
 # local filesystem layouts in the process.
 package PublicInbox::SolverGit;
 use strict;
diff --git a/lib/PublicInbox/ b/lib/PublicInbox/
index d88b34da..83b622fb 100644
--- a/lib/PublicInbox/
+++ b/lib/PublicInbox/
@@ -149,7 +149,7 @@ EOF
 id=R><b>Reply instructions:</b>
-You may reply publically to <a
+You may reply publicly to <a
 href=#t>this message</a> via plain-text email
 using any one of the following methods:

      parent reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-24 22:09 [PATCH 0/5] build, website, and speling updates Eric Wong
2020-01-24 22:09 ` [PATCH 1/5] doc: avoid needless rebuilds of NEWS Eric Wong
2020-01-24 22:09 ` [PATCH 2/5] website: re-add top-level files Eric Wong
2020-01-24 22:09 ` [PATCH 3/5] doc: INSTALL describe required deps for released versions Eric Wong
2020-01-24 22:09 ` [PATCH 4/5] website: omit technical/ and other subdirs Eric Wong
2020-01-24 22:09 ` 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

user/dev discussion of public-inbox itself

Archives are clonable:
	git clone --mirror
	git clone --mirror http://czquwvybam4bgbro.onion/meta
	git clone --mirror http://hjrcffqmbrq6wope.onion/meta
	git clone --mirror http://ou63pmih66umazou.onion/meta

Example config snippet for mirrors

Newsgroups are available over NNTP:

 note: .onion URLs require Tor:

AGPL code for this site: git clone