From: Tom Wijsman <TomWij@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: williamh@gentoo.org
Subject: Re: [gentoo-dev] gentoo-x86 tree cleanup for 'DESCRIPTION ends with a '.' character' warnings
Date: Wed, 13 Aug 2014 10:38:45 +0200 [thread overview]
Message-ID: <20140813103845.045f2d70@gentoo.org> (raw)
In-Reply-To: <20140812014820.GA3086@linux1>
[-- Attachment #1: Type: text/plain, Size: 1393 bytes --]
On Mon, 11 Aug 2014 20:48:20 -0500
William Hubbs <williamh@gentoo.org> wrote:
> On Sun, Aug 10, 2014 at 03:22:11PM +0300, Sergei Trofimovich wrote:
> > Hello World!
> >
> > TL;DR:
> > This evening I plan to mangle ~3000 ebuilds in the main tree
> > by dropping trailing '.' in all 'DESCRIPTION=' fields (except
> > "etc." case)
> >
> > Long story:
> >
> > As you may know newest portage release 2.2.11
> > got a minor (but chatty) QA warning:
> > DESCRIPTION ends with a '.' character
>
> Why is this a QA warning in the first place?
It isn't or shouldn't be; in the future, it would be nice if this type
passes by QA / Council before being acked into the Portage tree code.
Looking at the commit, the ack / commit has completely bypassed QA; we
also were not involved on the related bug, thus we were unaware of it.
> I don't recall a policy mandating that descriptions can't end with
> '.'. I asked our QA lead about it and was told that he didn't recall
> that we have an official policy about it either. Also, the devmanual
> never mentions any such requirement.
It has been a common belief to drop '.' among some from what I've seen.
--
With kind regards,
Tom Wijsman (TomWij)
Gentoo Developer
E-mail address : TomWij@gentoo.org
GPG Public Key : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-08-13 8:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-10 12:22 [gentoo-dev] gentoo-x86 tree cleanup for 'DESCRIPTION ends with a '.' character' warnings Sergei Trofimovich
2014-08-11 20:34 ` Bertrand Jacquin
2014-08-12 18:32 ` Michał Górny
2014-08-12 1:48 ` William Hubbs
2014-08-12 1:59 ` Manuel Rüger
2014-08-12 2:42 ` William Hubbs
2014-08-12 4:20 ` Tyler Pohl
2014-08-12 5:29 ` [gentoo-dev] " Duncan
2014-08-12 11:33 ` Alex Xu
2014-08-12 12:47 ` [gentoo-dev] " hasufell
2014-08-12 13:26 ` Rich Freeman
2014-08-12 14:26 ` hasufell
2014-08-12 16:24 ` William Hubbs
2014-08-12 18:37 ` Chris Reffett
2014-08-12 21:08 ` hasufell
2014-08-12 13:54 ` Ian Stakenvicius
2014-08-12 14:04 ` [gentoo-dev] repoman --nonag (was Re: gentoo-x86 tree cleanup for 'DESCRIPTION ends with a '.' character' warnings ) Ian Stakenvicius
2014-08-12 16:36 ` Rich Freeman
2014-08-12 16:57 ` Ian Stakenvicius
2014-08-12 17:08 ` hasufell
2014-08-12 17:13 ` Ian Stakenvicius
2014-08-12 17:25 ` Rich Freeman
2014-08-12 17:46 ` William Hubbs
2014-08-12 19:01 ` Michał Górny
2014-08-12 19:11 ` Ian Stakenvicius
2014-08-13 8:47 ` Tom Wijsman
2014-08-12 18:46 ` [gentoo-dev] gentoo-x86 tree cleanup for 'DESCRIPTION ends with a '.' character' warnings Michał Górny
2014-08-18 14:10 ` Ben de Groot
2014-08-13 8:38 ` Tom Wijsman [this message]
2014-08-13 16:36 ` [gentoo-dev] " Duncan
2014-08-12 22:00 ` [gentoo-dev] " Alexander Berntsen
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=20140813103845.045f2d70@gentoo.org \
--to=tomwij@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=williamh@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