public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Helge Kreutzmann <debian@helgefjell.de>,
	Seth David Schoen <schoen@loyalty.org>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Dear linux man-pages maintainer,
Date: Sun, 12 Mar 2023 12:05:40 +0100	[thread overview]
Message-ID: <cfbeaf79-c6a2-05bd-6618-63aed8482135@gmail.com> (raw)
In-Reply-To: <20230312060256.GJ7927@Debian-50-lenny-64-minimal>


[-- Attachment #1.1: Type: text/plain, Size: 808 bytes --]

Hi Helge,

On 3/12/23 07:02, Helge Kreutzmann wrote:
> 
> I just wonder if reporting "errors" like these in man-pages makes
> sense.

Yes, it makes sense :)

> Looking at this conversion you are very well aware of all the
> details of English, so my 5 cents are probably more distracting /
> confusing than helpful?

Nope, not distracting at all.  They help me notice details I didn't
think of (I've already applied many patches thanks to your reports.

Please continue reporting stuff you find.  If I later discard some
of them is not a problem.  Some others will help fix things.

> (Though I learn a lot form them).
> 
> Greetings
> 
>         Helge

Cheers,

Alex

> 

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2023-03-12 11:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-11 17:13 Dear linux man-pages maintainer, Helge Kreutzmann
2023-03-11 18:56 ` Seth David Schoen
2023-03-11 19:51   ` Helge Kreutzmann
2023-03-11 23:29   ` Alejandro Colomar
2023-03-11 23:38     ` Alejandro Colomar
2023-03-12  5:20     ` Helge Kreutzmann
2023-03-12  5:47       ` Seth David Schoen
2023-03-12  6:02         ` Helge Kreutzmann
2023-03-12 11:05           ` Alejandro Colomar [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=cfbeaf79-c6a2-05bd-6618-63aed8482135@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=debian@helgefjell.de \
    --cc=linux-man@vger.kernel.org \
    --cc=mario.blaettermann@gmail.com \
    --cc=schoen@loyalty.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