From: Kyle Meyer <kyle@kyleam.com>
To: Eric Wong <e@yhbt.net>
Cc: meta@public-inbox.org
Subject: Re: [PATCH 1/2] README: expand on the GUI non-requirement
Date: Wed, 01 Apr 2020 21:33:09 +0000 [thread overview]
Message-ID: <87r1x67uy2.fsf@kyleam.com> (raw)
In-Reply-To: <20200401203443.GA25378@dcvr>
Eric Wong <e@yhbt.net> writes:
> Thanks and good point about the run-on sentence.
>
> "as" could work, I think, the sentence may just be too long.
> Perhaps just a separate sentence:
>
> "communication. Users ..."
>
> Thoughts?
A separate sentence reads well to me. Thanks.
next prev parent reply other threads:[~2020-04-01 21:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 6:04 [PATCH 0/2] doc: pre-release doc updates Eric Wong
2020-04-01 6:04 ` [PATCH 1/2] README: expand on the GUI non-requirement Eric Wong
2020-04-01 15:30 ` Kyle Meyer
2020-04-01 20:34 ` Eric Wong
2020-04-01 21:33 ` Kyle Meyer [this message]
2020-04-01 23:40 ` Eric Wong
2020-04-02 0:26 ` Kyle Meyer
2020-04-02 5:54 ` [PATCH] README: add a missing "be" Eric Wong
2020-04-01 6:04 ` [PATCH 2/2] doc: update notes and HACKING ahead of 1.4 release Eric Wong
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r1x67uy2.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=e@yhbt.net \
--cc=meta@public-inbox.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).