From: bugzilla-daemon@bugzilla.kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 213013] getopt.3: further clarify behaviour
Date: Mon, 28 Jun 2021 19:30:20 +0000 [thread overview]
Message-ID: <bug-213013-11311-GxcSpQSkXg@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213013-11311@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=213013
--- Comment #5 from Alejandro Colomar (man-pages) (alx.manpages@gmail.com) ---
Hi James,
Sorry for the delay!
(In reply to James Hunt from comment #4)
> Thanks again for reviewing. I've updated the patch but I still think it
> needs to be "spelt out" that two plus symbols may be required since that
> avoids any confusion.
Okay.
> Also, I'm afraid I'm using a webmailer so submitting patches to a mailing
> list is going to be painful for me, whereas this bugzilla is quick and easy
> (and doesn't require me to register,
BTW, you don't need to subscribe to <linux-man@vger.kernel.org> to post there
:-)
But, I understand the rest.
> format mails in particular ways, plus
> of course to manage a ton more emails ;) But if the real action is happening
> on the ML, I wonder if in the future it might be possible to forward all
> bugzilla activity automatically to the ML rather than _vice versa_?
Yes. After you said these, I remembered that I asked about that some time ago.
The ML was subscribed again to this bugzilla activity :)
Now the review:
Could you please use '.IR ...' instead of '\fI...\fP...'?
See this extract from man-manpages(7):
[[
The preferred way to write this in the source file is:
.BR fcntl ()
(Using this format, rather than the use of "\fB...\fP()"
makes it easier to write tools that parse man page source
files.)
]]
> Thanks again for your help.
Thank you!
Alex
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
parent reply other threads:[~2021-06-28 19:30 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-213013-11311@https.bugzilla.kernel.org/>]
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=bug-213013-11311-GxcSpQSkXg@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-man@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).