From: Alexander Stein <alexander.stein@mailbox.org>
To: Bartosz Golaszewski <brgl@bgdev.pl>, Kent Gibson <warthog618@gmail.com>
Cc: "open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [libgpiod] [PATCH 0/5] Documentation improvements
Date: Tue, 11 Aug 2020 20:24:29 +0200 [thread overview]
Message-ID: <2066152.rvAzjVaaYW@kongar> (raw)
In-Reply-To: <20200811013950.GA25507@sol>
Am Dienstag, 11. August 2020, 03:39:50 CEST schrieb Kent Gibson:
> On Mon, Aug 10, 2020 at 06:49:21PM +0200, Bartosz Golaszewski wrote:
> > 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)?
> >
>
> For reference, I get some of the warnings addressed with doxygen 1.8.17
> in my setup.
> I don't get the a4wide (patch 3) so that might be new in 1.8.18, or
> otherwise dependent on setup??
>
> Either way, it would be useful for the patch to mention what version
> of doxygen is being targetted so everyone is on the same page.
Yes, I'm on 1.8.18, current release for archlinux. You are right, I should
have mentioned it in the patch though, sorry aobut that.
Best regards,
Alexander
next prev parent reply other threads:[~2020-08-11 18:24 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 ` [libgpiod] [PATCH 0/5] Documentation improvements Bartosz Golaszewski
2020-08-11 1:39 ` Kent Gibson
2020-08-11 18:24 ` Alexander Stein [this message]
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=2066152.rvAzjVaaYW@kongar \
--to=alexander.stein@mailbox.org \
--cc=brgl@bgdev.pl \
--cc=linux-gpio@vger.kernel.org \
--cc=warthog618@gmail.com \
/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).