From: Mike Frysinger <vapier@gentoo.org>
To: newlib@sourceware.org
Subject: Re: [PATCH] libgloss: doc: fix dir info entry usage
Date: Mon, 22 Jan 2024 22:17:34 -0500 [thread overview]
Message-ID: <Za8vzgty93wZhRY8@vapier> (raw)
In-Reply-To: <Za48Ualym3BI7fl0@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 650 bytes --]
On 22 Jan 2024 10:58, Corinna Vinschen wrote:
> 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)
>
> just push them.
thx, i pushed all but one i posted as RFC, so if you could check it:
https://sourceware.org/pipermail/newlib/2023/020842.html
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-01-23 3:17 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
2024-01-23 3:17 ` Mike Frysinger [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=Za8vzgty93wZhRY8@vapier \
--to=vapier@gentoo.org \
--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).