From: John Darrington <john@darrington.wattle.id.au>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Definite article in synopsis
Date: Fri, 23 Sep 2016 06:53:23 +0200 [thread overview]
Message-ID: <20160923045323.GB23992@jocasta.intra> (raw)
In-Reply-To: <20160923001551.GE12170@jasmine>
[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]
On Thu, Sep 22, 2016 at 08:15:51PM -0400, 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?
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.
I don't follow the reasoning. Makeing such a change on core-updates instead of
master would only make the merge effort worse.
J'
--
Avoid eavesdropping. Send strong encrypted email.
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2016-09-23 4:53 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
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 [this message]
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=20160923045323.GB23992@jocasta.intra \
--to=john@darrington.wattle.id.au \
--cc=guix-devel@gnu.org \
--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).