From: Jeroen Roovers <jer@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: About DESCRIPTION in ebuilds needing to end with a dot "."
Date: Mon, 22 Oct 2012 06:42:15 +0200 [thread overview]
Message-ID: <20121022064215.1cb91823@marga.jer-c2.orkz.net> (raw)
In-Reply-To: <20121020223504.3fe6c346@gentoo.org>
On Sat, 20 Oct 2012 22:35:04 -0600
Ryan Hill <dirtyepic@gentoo.org> wrote:
> I'm assuming that since we're now having dozen-post threads about
> whether or not to have periods in our descriptions that all the hard
> stuff has been solved?
Perhaps in planning QA, for now, but certainly not in executing it.
Documentation is lacking, too, and then some people still wouldn't read
it anyway, and with more EAPI changes we keep adding more ways to screw
it up, so please stand still while we reinvent the wheels on your desk
chair.
> Sweet, I'll prepare my repoman patch to enforce two spaces between
> sentences in Changelogs. (mwahahahaha)
Don't think for a minute you can foil my scheme to enforce slashes at
the end of URLs when not followed by paths.
jer
next prev parent reply other threads:[~2012-10-22 4:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 19:01 [gentoo-dev] About DESCRIPTION in ebuilds needing to end with a dot "." Pacho Ramos
2012-10-19 19:27 ` Doug Goldstein
2012-10-19 19:36 ` Thomas Sachau
2012-10-19 21:25 ` vivo75
2012-10-20 10:09 ` Ulrich Mueller
2012-10-20 16:51 ` Jeroen Roovers
2012-10-19 20:17 ` Alexandre Rostovtsev
2012-10-19 20:37 ` Michał Górny
2012-10-19 22:37 ` Rich Freeman
2012-10-20 6:09 ` Pacho Ramos
2012-10-20 14:27 ` Peter Stuge
2012-10-20 14:32 ` Pacho Ramos
2012-10-20 16:14 ` Michał Górny
2012-10-20 10:12 ` Samuli Suominen
2012-10-21 1:34 ` Ben de Groot
2012-10-21 6:37 ` Pacho Ramos
2012-10-21 4:35 ` [gentoo-dev] " Ryan Hill
2012-10-22 4:42 ` Jeroen Roovers [this message]
2012-10-30 7:18 ` [gentoo-dev] " Mike Frysinger
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=20121022064215.1cb91823@marga.jer-c2.orkz.net \
--to=jer@gentoo.org \
--cc=gentoo-dev@lists.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