aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKyle Meyer <kyle@kyleam.com>2021-02-06 13:06:28 -0500
committerKyle Meyer <kyle@kyleam.com>2021-02-07 12:36:52 -0500
commit5d908ac0e0e3b31eabc0f0bcccafdec5abfdfaf4 (patch)
tree275c5bfec9dfd3d93c0b8bb85ff460bbe6a0ac66
parent0a3de9e528c010e3f8ff113eaca28f10ad0528ca (diff)
downloadpiem-5d908ac0e0e3b31eabc0f0bcccafdec5abfdfaf4.tar.gz
manual: contributing: Remove some unnecessary bits
Cut off part of a sentence that adds no additional information, and discard a footnote. Message-Id: <20210206180630.3676-2-kyle@kyleam.com>
-rw-r--r--piem.texi8
1 files changed, 3 insertions, 5 deletions
diff --git a/piem.texi b/piem.texi
index 070adf4..ecd17e6 100644
--- a/piem.texi
+++ b/piem.texi
@@ -449,11 +449,9 @@ Patches, bug reports, and other feedback are welcome. Please send a
plain-text email to @email{piem@@inbox.kyleam.com}. Messages that
include this address are public and available as public-inbox archives
at @url{https://inbox.kyleam.com/piem}. Note that this is not a mailing
-list, and there are no subcribers. Updates can be followed through one
-of public-inbox's pull methods (@pxref{public-inbox}). This means it is
-particularly important to @emph{not} drop participants when replying
-@footnote{@dots{} and in this author's opinion, doing so is a bad
-practice anyway.}.
+list. Updates can be followed through one of public-inbox's pull
+methods (@pxref{public-inbox}). This means it is particularly important
+to @emph{not} drop participants when replying.
You can, unsurprisingly, use piem to work on piem by adding an entry
like this to @code{piem-inboxes}.