public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] repoman --nonag (was Re: gentoo-x86 tree cleanup for 'DESCRIPTION ends with a '.' character' warnings )
Date: Tue, 12 Aug 2014 12:46:45 -0500	[thread overview]
Message-ID: <20140812174645.GA8605@linux1> (raw)
In-Reply-To: <CAGfcS_nkqY243x36svwVXdXiMr653JbJxEUhkd_xX=da9-RFoQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]

On Tue, Aug 12, 2014 at 01:25:44PM -0400, Rich Freeman wrote:
> On Tue, Aug 12, 2014 at 1:13 PM, Ian Stakenvicius <axs@gentoo.org> wrote:
> >
> > I don't consider a recommended style message to be 'broken' just
> > because it's not listed in the devmanual/PMS/etc as a requirement.
> > The implementation of it, on the other hand, yes that could be broken
> > and in this case should be fixed if we keep the check around.
> >
> 
> If we are bothered enough by something to have repoman check it, we
> can be bothered enough to add it to the devmanual.

I also think "that something" should be added to the devmanual before it
is added to repoman so that developers aren't blind-sided by repoman
warnings like this.


> I think we need to decide whether we care about periods at the ends of
> DESCRIPTIONs.  If we do, then it should be a warning and devs should
> fix their ebuilds at the next convenient opportunity.  If we don't,
> then let's just drop the warning.
 
I think some will have periods and some won't depending on how the
description is written, so this warning is not one that should stay.

William


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2014-08-12 17:46 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 [this message]
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=20140812174645.GA8605@linux1 \
    --to=williamh@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