From: hasufell <hasufell@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] gentoo-x86 tree cleanup for 'DESCRIPTION ends with a '.' character' warnings
Date: Tue, 12 Aug 2014 12:47:02 +0000 [thread overview]
Message-ID: <53EA0CC6.6050000@gentoo.org> (raw)
In-Reply-To: <20140812024257.GA3262@linux1>
William Hubbs:
> On Tue, Aug 12, 2014 at 03:59:30AM +0200, Manuel Rüger wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA512
>
> *snip*
>
>> These links might be helpful:
>>
>> http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=06637c4215d55c57517739214c6e0fd6f8f53914
>>
>> https://bugs.gentoo.org/show_bug.cgi?id=438976
>>
>> http://comments.gmane.org/gmane.linux.gentoo.devel/80786
>>
>>
>> What's still missing is a patch for devmanual (if we still really want
>> to enforce this).
>
> I read the thread, and there was no concensus about making this a
> repoman check. Some people thought it was a good idea, but there was a
> feeling that this sort of thing is trivial and shouldn't be worried
> about.
>
That thread is pretty odd.
First, a sentence does not need to have a predicate. I know that for 99%
sure in german and the english wikipedia article seems to suggest the
same. Correct me if I am wrong.
Second, there are valid descriptions that are full ordinary sentences
without referencing ${PN}:
"Access a working SSH implementation by means of a library".
In addition, repoman doesn't check for full sentences that reference
${PN}, such as:
"Portage is the package management and distribution system for Gentoo".
So we have another (useless) repoman warning with false positives.
next prev parent reply other threads:[~2014-08-12 12:47 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 ` hasufell [this message]
2014-08-12 13:26 ` [gentoo-dev] " 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
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=53EA0CC6.6050000@gentoo.org \
--to=hasufell@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