From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH] libgloss: doc: fix dir info entry usage
Date: Mon, 22 Jan 2024 10:58:41 +0100 [thread overview]
Message-ID: <Za48Ualym3BI7fl0@calimero.vinschen.de> (raw)
In-Reply-To: <ZasY8MAGNHD1o_rH@vapier>
Hi Mike,
On Jan 19 19:50, Mike Frysinger wrote:
> On 26 Dec 2023 19:50, Mike Frysinger wrote:
> > Wrapping the dir info with @ifnottex means it's included in all other
> > outputs like html which makes no sense. Switch to @direntry which is
> > specific for this content and is automatically written to the output
> > that makes sense, and omitted from the rest.
>
> ping ...
>
> (and the other doc update patches too)
> -mike
just push them.
Thanks,
Corinna
next prev parent reply other threads:[~2024-01-22 9:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 0:50 Mike Frysinger
2024-01-20 0:50 ` Mike Frysinger
2024-01-22 9:58 ` Corinna Vinschen [this message]
2024-01-23 3:17 ` Mike Frysinger
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=Za48Ualym3BI7fl0@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=newlib@sourceware.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).