From: Ben Woodcroft <b.woodcroft@uq.edu.au>
To: Leo Famulari <leo@famulari.name>,
John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel@gnu.org
Subject: Re: Definite article in synopsis
Date: Fri, 23 Sep 2016 10:32:56 +1000 [thread overview]
Message-ID: <6d27b754-5fa2-1fda-8d0a-431ef224b7ef@uq.edu.au> (raw)
In-Reply-To: <20160923001551.GE12170@jasmine>
On 09/23/2016 10:15 AM, Leo Famulari wrote:
> On Wed, Sep 21, 2016 at 12:59:51PM +0200, John Darrington wrote:
>> I thought we had a policy that the synopsis field must not
>> start with an article.
>>
>> However running
>> grep 'synopsis *"The' *.scm
>>
>> shows that we have many instances where this policy is
>> not followed.
>>
>> Or have I misunderstood something?
> It's a minor issue. I think that making many small changes throughout
> the master branch will be too disruptive for what is a relatively minor
> style issue.
This is true even though changing a description doesn't trigger a rebuild?
> If the change is made, I'd prefer it on core-updates. Merging master
> into core-updates and vice versa already requires somebody to resolve a
> lot of merge conflicts. I'd rather not add to that burden.
Do you have any recommendations for changing our practices to ease this
issue?
ben
next prev parent reply other threads:[~2016-09-23 0:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 10:59 Definite article in synopsis John Darrington
2016-09-23 0:15 ` Leo Famulari
2016-09-23 0:32 ` Ben Woodcroft [this message]
2016-09-23 5:10 ` Leo Famulari
2016-09-24 2:28 ` Ludovic Courtès
2016-09-24 2:53 ` Leo Famulari
2016-09-23 4:53 ` John Darrington
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6d27b754-5fa2-1fda-8d0a-431ef224b7ef@uq.edu.au \
--to=b.woodcroft@uq.edu.au \
--cc=guix-devel@gnu.org \
--cc=john@darrington.wattle.id.au \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).