From: Christopher Baines <mail@cbaines.net>
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: 28830@debbugs.gnu.org
Subject: [bug#28830] [PATCH] gnu: Add emacs-ggtags.
Date: Tue, 31 Oct 2017 08:22:18 +0000 [thread overview]
Message-ID: <20171031082218.2a45cfab@cbaines.net> (raw)
In-Reply-To: <87zi8r1jfk.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1194 bytes --]
On Mon, 16 Oct 2017 13:22:23 +0300
Oleg Pykhalov <go.wigust@gmail.com> wrote:
> Hello Christopher,
>
> Christopher Baines <mail@cbaines.net> writes:
>
> [...]
>
> >> + (synopsis "Frontend to GNU Global source code tagging system")
> >
> > I'd suggest putting "the" in here, so "Frontend to the GNU Global ...",
> > as I think that reads better.
>
> [...]
>
> > Similarly with "the GNU Global" in the description. What do you think?
> > Apart from that, this looks fine to me :)
>
> I don't think so. Upstream¹ doesn't have an article “the” before GNU
> Global, too. WDYT?
>
> ¹ http://elpa.gnu.org/packages/ggtags.html
I don't think there is any harm in improving on the descriptions of the
software from the upstream source. But I'll leave it up to you to make
the decision.
Unfortunately, I don't have a very formal understanding of English
grammar, but there is some information about definite articles [1].
Which I think says that its appropriate to use as there is one,
specific "GNU Global source code tagging system".
1: https://learnenglish.britishcouncil.org/en/english-grammar/determiners-and-quantifiers/definite-article
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next prev parent reply other threads:[~2017-10-31 8:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-14 9:04 [bug#28830] [PATCH] gnu: Add emacs-ggtags Oleg Pykhalov
2017-10-16 5:51 ` Christopher Baines
2017-10-16 10:22 ` Oleg Pykhalov
2017-10-31 8:22 ` Christopher Baines [this message]
2017-10-31 17:11 ` bug#28830: " Oleg Pykhalov
2017-10-31 19:39 ` [bug#28830] " Tobias Geerinckx-Rice
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=20171031082218.2a45cfab@cbaines.net \
--to=mail@cbaines.net \
--cc=28830@debbugs.gnu.org \
--cc=go.wigust@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.