From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH] scripts: add README to describe its purpose
Date: Wed, 5 Jun 2019 02:21:12 +0000 [thread overview]
Message-ID: <20190605022112.29431-1-e@80x24.org> (raw)
Well, it could probably be moved to contrib...
---
scripts/README | 6 ++++++
1 file changed, 6 insertions(+)
create mode 100644 scripts/README
diff --git a/scripts/README b/scripts/README
new file mode 100644
index 0000000..3b9c37d
--- /dev/null
+++ b/scripts/README
@@ -0,0 +1,6 @@
+This directory contains informal scripts and random tools used
+in the development of public-inbox. Some only exist only for
+historical purposes, and some may not work anymore.
+
+See the "script/" directory (not "scripts/") for supported and
+documented commands.
--
EW
reply other threads:[~2019-06-05 2:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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: http://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190605022112.29431-1-e@80x24.org \
--to=e@80x24.org \
--cc=meta@public-inbox.org \
/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
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
https://80x24.org/public-inbox.git
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).