discussion and development of piem
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: piem@inbox.kyleam.com
Subject: [PATCH 1/3] manual: contributing: Remove some unnecessary bits
Date: Sat,  6 Feb 2021 13:06:28 -0500
Message-ID: <20210206180630.3676-2-kyle@kyleam.com> (raw)
In-Reply-To: <20210206180630.3676-1-kyle@kyleam.com>

Cut off part of a sentence that adds no additional information, and
discard a footnote.
---
 piem.texi | 8 +++-----
 1 file 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 @@ Contributing
 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}.
-- 
2.30.0


  reply	other threads:[~2021-02-06 18:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-06 18:06 [PATCH 0/3] manual: Point to range-diff and related projects Kyle Meyer
2021-02-06 18:06 ` Kyle Meyer [this message]
2021-02-06 18:06 ` [PATCH 2/3] manual: contributing: Mention range-diff Kyle Meyer
2021-02-06 18:06 ` [PATCH 3/3] manual: Add a "Related projects and tools" section Kyle Meyer

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://git.kyleam.com/

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

  git send-email \
    --in-reply-to=20210206180630.3676-2-kyle@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=piem@inbox.kyleam.com \
    --subject='Re: [PATCH 1/3] manual: contributing: Remove some unnecessary bits' \
    /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

discussion and development of piem

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.kyleam.com/piem/0 piem/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 piem piem/ https://inbox.kyleam.com/piem \
		piem@inbox.kyleam.com
	public-inbox-index piem

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://news.yhetil.org/yhetil.emacs.piem


code repositories for project(s) associated with this inbox:

	https://git.kyleam.com/piem/

AGPL code for this site: git clone http://ou63pmih66umazou.onion/public-inbox.git