From: Ben de Groot <yngwin@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] gentoo-x86 tree cleanup for 'DESCRIPTION ends with a '.' character' warnings
Date: Mon, 18 Aug 2014 22:10:35 +0800 [thread overview]
Message-ID: <CAB9SyzTPp1H_s4XMhHxqrdymiioLKuyzio3-VXrk9E0qvjq9xg@mail.gmail.com> (raw)
In-Reply-To: <20140812204614.1b9be84d@pomiot.lan>
On 13 August 2014 02:46, Michał Górny <mgorny@gentoo.org> wrote:
> Dnia 2014-08-11, o godz. 20:48:20
> William Hubbs <williamh@gentoo.org> napisał(a):
>> > got a minor (but chatty) QA warning:
>> > DESCRIPTION ends with a '.' character
>>
>> Why is this a QA warning in the first place?
>
> Because it is a common mistake, and having the warning in-place should
> help people avoid repeating it.
This is correct.
>> 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.
>
> I don't know if and where it is documented but that's what I was taught
> when I started contributing to Gentoo, and it pretty much follows
> the common sense. DESCRIPTION is supposed to be short and descriptive.
> So you do an elliptical sentence (if I got the right translation),
> and that doesn't end with a dot.
Again, this is what I was taught as well. It may have been an
undocumented rule, but it has been around for as long as I can
remember. It also makes linguistic sense, and as an English teacher it
always irks me when I see this mistake.
> If you have any fair reason to not follow this, please speak of it.
> Otherwise, this is pure bikeshed and waste of time. This thread already
> took much more time than fixing your packages if repoman complained
> about them.
Amen!
>> If someone can point me to something I'm missing, let me know.
>> Otherwise, I think the warning should be removed.
>
> Even if there were no written-down policy, why would it be removed?
> What is the benefit of removing the check that resulted in many fixes
> already? Do you want to revert the removals afterwards? Or do you want
> to introduce new packages which use '.' there?
I completely support this argument. The warning is correct and should
remain in place.
--
Cheers,
Ben | yngwin
Gentoo developer
next prev parent reply other threads:[~2014-08-18 14:10 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 [this message]
2014-08-13 8:38 ` Tom Wijsman
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=CAB9SyzTPp1H_s4XMhHxqrdymiioLKuyzio3-VXrk9E0qvjq9xg@mail.gmail.com \
--to=yngwin@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