discussion and development of piem
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: piem@inbox.kyleam.com
Subject: [PATCH 0/2] README updates
Date: Sun, 12 Dec 2021 17:21:17 -0500	[thread overview]
Message-ID: <20211212222119.124669-1-kyle@kyleam.com> (raw)

Sean Whitton suggested that piem's README should point to mailscripts
(and vice versa) [*].  I haven't given much attention to the README,
hoping it has just enough to make people go to the documentation
(where mailscripts and other related projects are mentioned).
However, it does seem like a good idea for the README to link
mailscripts (and git-email) to increase the chances of helping someone
discover a tool that might be useful to them.

And while there, refresh the description of piem's functionality a

  [1/2] README: Mention b4 and lei
  [2/2] README: Point to related projects

 README | 27 ++++++++++++++++++++++++---
 1 file changed, 24 insertions(+), 3 deletions(-)

[*]: https://inbox.kyleam.com/piem/YbZOh0yEFLBwVUMp@melete.silentflame.com/

base-commit: e519aa44d148d5b8f22d7fe8844dc566046b04c2

             reply	other threads:[~2021-12-12 22:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-12 22:21 Kyle Meyer [this message]
2021-12-12 22:21 ` [PATCH 1/2] README: Mention b4 and lei Kyle Meyer
2021-12-12 22:21 ` [PATCH 2/2] README: Point to related projects 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:

  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=20211212222119.124669-1-kyle@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=piem@inbox.kyleam.com \


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