From: "W. Trevor King" <wking@tremily.us>
To: notmuch@notmuchmail.org
Cc: David Bremner <david@tethera.net>,
Tomi Ollila <tomi.ollila@iki.fi>, Jani Nikula <jani@nikula.org>,
Carl Worth <cworth@cworth.org>,
"W. Trevor King" <wking@tremily.us>
Subject: [PATCH 0/5] notmuch-report: Rename from nmbug-status and add man pages
Date: Fri, 1 Jan 2016 22:08:00 -0800 [thread overview]
Message-ID: <cover.1451714099.git.wking@tremily.us> (raw)
Spun off from discussion here [1]. I've just shifted nmbug-status in
this series, and left nmbug alone for now. If/when this series lands,
it will be easy to handle a nmbug rename in a subsequent series.
Note that while I think the renames from nmbug-status to
notmuch-report and status-config.json to notmuch-report.json are
useful changes, they will break backwards compatibility for existing
users. I'm not sure how many existing users there are, and I expect
the NEWS entry will clue them in. But if folks want a temporary
fallback to status-config.json in the absence of notmuch-report.json,
I can add that in a v2.
Cheers,
Trevor
[1]: id:m2twmxbl1i.fsf@guru.guru-group.fi
http://thread.gmane.org/gmane.mail.notmuch.general/21535/focus=21539
W. Trevor King (5):
nmbug-status: Avoid hard-coded filename in error message
notmuch-report: Rename from nmbug-status
notmuch-report.json: Rename from status-config.json
notmuch-report: Add notmuch-report(1) and notmuch-report.json(5) man
pages
NEWS: Document the notmuch-report branch
NEWS | 26 ++
devel/nmbug/doc/.gitignore | 2 +
devel/nmbug/doc/Makefile | 38 +++
devel/nmbug/doc/conf.py | 67 ++++
devel/nmbug/doc/index.rst | 17 +
devel/nmbug/doc/man1/notmuch-report.1.rst | 54 ++++
devel/nmbug/doc/man5/notmuch-report.json.5.rst | 129 ++++++++
devel/nmbug/nmbug-status | 419 ------------------------
devel/nmbug/notmuch-report | 422 +++++++++++++++++++++++++
devel/nmbug/notmuch-report.json | 70 ++++
devel/nmbug/status-config.json | 70 ----
11 files changed, 825 insertions(+), 489 deletions(-)
create mode 100644 devel/nmbug/doc/.gitignore
create mode 100644 devel/nmbug/doc/Makefile
create mode 100644 devel/nmbug/doc/conf.py
create mode 100644 devel/nmbug/doc/index.rst
create mode 100644 devel/nmbug/doc/man1/notmuch-report.1.rst
create mode 100644 devel/nmbug/doc/man5/notmuch-report.json.5.rst
delete mode 100755 devel/nmbug/nmbug-status
create mode 100755 devel/nmbug/notmuch-report
create mode 100644 devel/nmbug/notmuch-report.json
delete mode 100644 devel/nmbug/status-config.json
--
2.1.0.60.g85f0837
next reply other threads:[~2016-01-02 6:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-02 6:08 W. Trevor King [this message]
2016-01-02 6:08 ` [PATCH 1/5] nmbug-status: Avoid hard-coded filename in error message W. Trevor King
2016-01-07 13:27 ` David Bremner
2016-01-02 6:08 ` [PATCH 2/5] notmuch-report: Rename from nmbug-status W. Trevor King
2016-01-03 16:19 ` Jani Nikula
2016-01-02 6:08 ` [PATCH 3/5] notmuch-report.json: Rename from status-config.json W. Trevor King
2016-01-02 6:08 ` [PATCH 4/5] notmuch-report: Add notmuch-report(1) and notmuch-report.json(5) man pages W. Trevor King
2016-01-02 6:08 ` [PATCH 5/5] NEWS: Document the notmuch-report branch W. Trevor King
2016-03-24 10:52 ` David Bremner
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1451714099.git.wking@tremily.us \
--to=wking@tremily.us \
--cc=cworth@cworth.org \
--cc=david@tethera.net \
--cc=jani@nikula.org \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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://yhetil.org/notmuch.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).