From: Patrice Clement <monsieurp@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: vim@gentoo.org
Subject: [gentoo-dev] [PATCH 0/2] vim-spell.eclass: improvements.
Date: Sat, 19 Aug 2017 14:53:48 +0200 [thread overview]
Message-ID: <20170819125350.10651-1-monsieurp@gentoo.org> (raw)
Hi everyone
I'm working on solving https://bugs.gentoo.org/469414 but realised much of the
eclass documentation isn't up to our standards. Here's a few commits to fix
that oversight.
Please review.
Thanks!
Patrice Clement (2):
vim-spell.eclass: document functions using Gentoo documentation tags.
vim-spell.eclass: document variables using Gentoo documentation tags.
eclass/vim-spell.eclass | 66 ++++++++++++++++++++++++++++++-------------------
1 file changed, 41 insertions(+), 25 deletions(-)
--
2.13.0
next reply other threads:[~2017-08-19 12:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-19 12:53 Patrice Clement [this message]
2017-08-19 12:53 ` [gentoo-dev] [PATCH 1/2] vim-spell.eclass: document functions using Gentoo documentation tags Patrice Clement
2017-08-19 12:53 ` [gentoo-dev] [PATCH 2/2] vim-spell.eclass: document variables " Patrice Clement
2017-08-19 18:14 ` Michał Górny
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=20170819125350.10651-1-monsieurp@gentoo.org \
--to=monsieurp@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=vim@gentoo.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