From: "Aaron W. Swenson" <titanofold@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "pr@gentoo.org" <pr@gentoo.org>
Subject: Re: [gentoo-dev] RFC v2: News item: Perl 5.26 update
Date: Sun, 8 Oct 2017 08:41:18 -0400 [thread overview]
Message-ID: <20171008124118.GF24569@gengoff> (raw)
In-Reply-To: <2321099.RaGxO3cglp@pinacolada>
[-- Attachment #1: Type: text/plain, Size: 307 bytes --]
On 2017-10-08 14:01, Andreas K. Huettel wrote:
> OK so here's the updated version:
> …
> Typical errors are
Needs a colon.
Typical errors are:
But the rest looks good to me.
I don’t know how to write “good job” without it sounding
patronizing. But here it is anyway: Good job!
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 376 bytes --]
prev parent reply other threads:[~2017-10-08 12:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-07 15:03 [gentoo-dev] RFC: News item: Perl 5.26 update Andreas K. Huettel
2017-10-07 15:21 ` Kent Fredric
2017-10-07 15:52 ` Andreas K. Huettel
2017-10-07 16:15 ` Aaron W. Swenson
2017-10-07 16:44 ` Kent Fredric
2017-10-08 12:01 ` [gentoo-dev] RFC v2: " Andreas K. Huettel
2017-10-08 12:41 ` Aaron W. Swenson [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=20171008124118.GF24569@gengoff \
--to=titanofold@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=pr@gentoo.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