public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: gentoo-x86 tree cleanup for 'DESCRIPTION ends with a '.' character' warnings
Date: Wed, 13 Aug 2014 16:36:13 +0000 (UTC)	[thread overview]
Message-ID: <pan$81705$6628db6f$7dc5f4f6$a7267dba@cox.net> (raw)
In-Reply-To: 20140813103845.045f2d70@gentoo.org

Tom Wijsman posted on Wed, 13 Aug 2014 10:38:45 +0200 as excerpted:

>> 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.

[Observational/skippable.]

FWIW, I've been watching this debate with some amusement, as I follow 
Language Log, which has a continuing serious covering the generational/
regional differences in period/full-stop interpretation.

The first in the series and my favorite, due to the cartoon illustrating 
the issue (Nov. 2012):

http://languagelog.ldc.upenn.edu/nll/?p=4304

Two newer installations of the series (Nov 2013 and Aug 1, 2014, 
respectively):

http://languagelog.ldc.upenn.edu/nll/?p=8667
http://languagelog.ldc.upenn.edu/nll/?p=13723


It can be a big deal for some.  Quoting from the first comment on the 
first article (and noting that what we call a "period" US-English is a 
"full stop" in UK-English):

Obviously, a period is a full stop, but, in short text messages, I feel 
like it almost SAYS full stop, with all the attendant emphasis of that 
phrase. "Best movie ever" is one thing, but "Best. Movie. Ever." is quite 
another.


Back to gentoo and the current "Much ado about nothing".  Someone's 
irritated with the periods/full-stops following short descriptions, 
because to him it's disruptive, almost as if an exclamation point (which 
I /would/ find disruptive) was used, such that for him a repoman check is 
warranted.

But to many others, it's trivial, certainly nothing worth bothering with 
a repoman check and hundreds of individual fixes with concurrent changelog 
entries.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman



  reply	other threads:[~2014-08-13 16:36 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
2014-08-13 16:36     ` Duncan [this message]
2014-08-12 22:00 ` 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='pan$81705$6628db6f$7dc5f4f6$a7267dba@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --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