From: Jon Turney <jon.turney@dronecode.org.uk>
To: Christian Franke <Christian.Franke@t-online.de>
Cc: cygwin-apps@cygwin.com
Subject: Re: [PATCH cygport] Use correct wording if only one package is announced
Date: Sun, 10 Mar 2024 17:20:43 +0000 [thread overview]
Message-ID: <9838dff0-dd92-47c3-aac6-546f89d284e7@dronecode.org.uk> (raw)
In-Reply-To: <fadecf95-47c1-6ac6-c785-2b920e034421@t-online.de>
On 23/02/2024 11:16, Christian Franke via Cygwin-apps wrote:
> Brian Inglis via Cygwin-apps wrote:
>> On 2024-02-21 07:25, Christian Franke via Cygwin-apps wrote:
>>
>> Change variable name from $s to $has or $s_have as variable $s usually
>> implies only the plural letter s or nothing; e.g.
>> ...
>> + local has="s have"
>> +
>> + [ $pkg_count != 1 ] || has=" has"
>> ...
>> +The following package${has} been uploaded to the Cygwin distribution:
>> ...
>
> Agree - new patch attached.
Applied. Thanks!
prev parent reply other threads:[~2024-03-10 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 14:25 Christian Franke
2024-02-21 21:36 ` Brian Inglis
2024-02-23 11:16 ` Christian Franke
2024-03-10 17:20 ` Jon Turney [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9838dff0-dd92-47c3-aac6-546f89d284e7@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=Christian.Franke@t-online.de \
--cc=cygwin-apps@cygwin.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.
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).