From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Vikas Talan <vikas.chaudhary2608@gmail.com>,
35275-done@debbugs.gnu.org, majordomo@vger.kernel.org,
lkml <linux-kernel@vger.kernel.org>,
linux-kernel-announce@vger.kernel.org,
Linux API <linux-api@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
libc-alpha-subscribe@sourceware.org,
libc-help-subscribe@sourceware.org, manpages@packages.debian.org,
listar@nl.linux.org, linux-man <linux-man@vger.kernel.org>
Subject: Re: bug#35275: spelling mistake manual pages
Date: Mon, 15 Apr 2019 13:08:17 +0200 [thread overview]
Message-ID: <CAKgNAkjAp89DfGynMs3v=29egqwouaZhUt993wpeu=t+257oCQ@mail.gmail.com> (raw)
In-Reply-To: <8970d433-8c7e-23d8-7d04-b9344adbf3ad@cs.ucla.edu>
But also, the report is simply wrong.
On Mon, 15 Apr 2019 at 07:34, Paul Eggert <eggert@cs.ucla.edu> wrote:
>
> That report appears to be about the glibc manual. Please report glibc bugs as
> described here:
>
> https://sourceware.org/glibc/wiki/FilingBugs
>
> Also, please use plain text rather than images to describe bugs in a text file.
prev parent reply other threads:[~2019-04-15 11:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABCHxwFMp+vFpv8V-c0=CeXnNmymEuvm_7adGnOnUfCUH7C5+w@mail.gmail.com>
2019-04-15 5:34 ` bug#35275: spelling mistake manual pages Paul Eggert
2019-04-15 11:08 ` Michael Kerrisk (man-pages) [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='CAKgNAkjAp89DfGynMs3v=29egqwouaZhUt993wpeu=t+257oCQ@mail.gmail.com' \
--to=mtk.manpages@gmail.com \
--cc=35275-done@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=libc-alpha-subscribe@sourceware.org \
--cc=libc-help-subscribe@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=listar@nl.linux.org \
--cc=majordomo@vger.kernel.org \
--cc=manpages@packages.debian.org \
--cc=netdev@vger.kernel.org \
--cc=vikas.chaudhary2608@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).