From: Corinna Vinschen <vinschen@redhat.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Jon Turney <jon.turney@dronecode.org.uk>, newlib@sourceware.org
Subject: Re: [PATCH 0/5] makedocbook improvements (v2)
Date: Mon, 7 Nov 2022 09:48:20 +0100 [thread overview]
Message-ID: <Y2jGVBR21VbSuYoG@calimero.vinschen.de> (raw)
In-Reply-To: <Y2ZzEr/fmoc6rvic@vapier>
On Nov 5 21:28, Mike Frysinger wrote:
> lgtm, thanks
> -mike
Thanks Mike!
Jon, please push.
Thanks,
Corinna
prev parent reply other threads:[~2022-11-07 8:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 13:49 Jon Turney
2022-11-04 13:49 ` [PATCH 1/5] makedocbook: Use raw strings for regexes Jon Turney
2022-11-04 13:49 ` [PATCH 2/5] makedocbook: Use sys.exit() Jon Turney
2022-11-04 14:52 ` Torbjorn SVENSSON
2022-11-05 14:28 ` Mike Frysinger
2022-11-04 13:49 ` [PATCH 3/5] makedocbook: Drop stray semicolons Jon Turney
2022-11-04 13:49 ` [PATCH 4/5] makedocbook: Adjust inline whitespace to fix flake8 warnings Jon Turney
2022-11-04 13:49 ` [PATCH 5/5] makedocbook: Fix false report of unhandled texinfo command Jon Turney
2022-11-05 14:28 ` [PATCH 0/5] makedocbook improvements (v2) Mike Frysinger
2022-11-07 8:48 ` Corinna Vinschen [this message]
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=Y2jGVBR21VbSuYoG@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=jon.turney@dronecode.org.uk \
--cc=newlib@sourceware.org \
--cc=vapier@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).