From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Alexander Stein <alexander.stein@mailbox.org>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [libgpiod] [PATCH 0/5] Documentation improvements
Date: Mon, 10 Aug 2020 18:49:21 +0200 [thread overview]
Message-ID: <CAMRc=MeVKBHgU6u5gVjzaysQuwrudo3Zun+AHDb74pGXzkB4dg@mail.gmail.com> (raw)
In-Reply-To: <20200808095944.188479-1-alexander.stein@mailbox.org>
On Sat, Aug 8, 2020 at 12:06 PM Alexander Stein
<alexander.stein@mailbox.org> wrote:
>
> Hey,
> this changeset improves the document generation by reducing warnings
> as well as supporting building doc out of tree now.
>
> Alexander Stein (5):
> doc: Fix doxygen warnings
> doc: Use autotoolized Doxyfile
> doc: Fix doxygen warning
> doc: Remove obsolete PERL_PATH
> doc: Add @file to headers
>
> .gitignore | 1 +
> Doxyfile => Doxyfile.in | 8 ++++----
> Makefile.am | 4 +---
> bindings/cxx/gpiod.hpp | 6 +++++-
> configure.ac | 1 +
> include/gpiod.h | 30 +++++++++++++++++-------------
> 6 files changed, 29 insertions(+), 21 deletions(-)
> rename Doxyfile => Doxyfile.in (93%)
>
> --
> 2.28.0
>
Thanks for sending those! I guess I don't see any of the warnings you
mention because doxygen on my laptop is too old (1.8.13)?
Bartosz
next prev parent reply other threads:[~2020-08-10 16:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-08 9:59 [libgpiod] [PATCH 0/5] Documentation improvements Alexander Stein
2020-08-08 9:59 ` [libgpiod] [PATCH 1/5] doc: Fix doxygen warnings Alexander Stein
2020-08-08 9:59 ` [libgpiod] [PATCH 2/5] doc: Use autotoolized Doxyfile Alexander Stein
2020-08-13 18:39 ` Bartosz Golaszewski
2020-08-08 9:59 ` [libgpiod] [PATCH 3/5] doc: Fix doxygen warning Alexander Stein
2020-08-08 9:59 ` [libgpiod] [PATCH 4/5] doc: Remove obsolete PERL_PATH Alexander Stein
2020-08-08 9:59 ` [libgpiod] [PATCH 5/5] doc: Add @file to headers Alexander Stein
2020-08-10 16:49 ` Bartosz Golaszewski [this message]
2020-08-11 1:39 ` [libgpiod] [PATCH 0/5] Documentation improvements Kent Gibson
2020-08-11 18:24 ` Alexander Stein
2020-08-11 18:59 ` Bartosz Golaszewski
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='CAMRc=MeVKBHgU6u5gVjzaysQuwrudo3Zun+AHDb74pGXzkB4dg@mail.gmail.com' \
--to=brgl@bgdev.pl \
--cc=alexander.stein@mailbox.org \
--cc=linux-gpio@vger.kernel.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).