From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] [PATCH 0/2] alfred: Convert CHANGELOG/README to reStructuredText
Date: Mon, 20 Nov 2017 22:02:21 +0100 [thread overview]
Message-ID: <20171120210223.9002-1-sven@narfation.org> (raw)
Hi,
I was talking today with Simon about the "License cleanup" changes. He
would prefer when the *.license files don't exist (when possible). Luckily,
I already wanted to convert these files (or at least the READMEs) to
reStructuredText and I've already shown in these patchsets how the
SPDX annotation should be done for the lrest files. So it was just
logically to immediately post the conversion to rst and integration
of this tag.
We've also discussed how the changelog should look like. It should be
simple and we only wanted to show the date (not the time) anymore.
And the actual changelog lists should be kept (mostly untouched - beside
some minor format fixes to make it reStructuredText compatible).
This patchset is based on the "alfred: License cleanup" patchset.
Kind regards,
Sven
Sven Eckelmann (2):
alfred: Convert CHANGELOG to reStructuredText
alfred: Convert README to reStructuredText
CHANGELOG | 169 ----------------------------
CHANGELOG.license | 2 -
CHANGELOG.rst | 175 +++++++++++++++++++++++++++++
README.license | 2 -
README => README.rst | 311 +++++++++++++++++++++++++++------------------------
5 files changed, 339 insertions(+), 320 deletions(-)
delete mode 100644 CHANGELOG
delete mode 100644 CHANGELOG.license
create mode 100644 CHANGELOG.rst
delete mode 100644 README.license
rename README => README.rst (55%)
--
2.11.0
next reply other threads:[~2017-11-20 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 21:02 Sven Eckelmann [this message]
2017-11-20 21:02 ` [B.A.T.M.A.N.] [PATCH 1/2] alfred: Convert CHANGELOG to reStructuredText Sven Eckelmann
2017-11-20 21:02 ` [B.A.T.M.A.N.] [PATCH 2/2] alfred: Convert README " Sven Eckelmann
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171120210223.9002-1-sven@narfation.org \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.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.
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 NNTP newsgroup(s).