From: Eric Wong <e@yhbt.net>
To: Kyle Meyer <kyle@kyleam.com>
Cc: meta@public-inbox.org
Subject: Re: [PATCH 1/2] README: expand on the GUI non-requirement
Date: Wed, 1 Apr 2020 23:40:54 +0000 [thread overview]
Message-ID: <20200401234054.GA32225@dcvr> (raw)
In-Reply-To: <87r1x67uy2.fsf@kyleam.com>
Kyle Meyer <kyle@kyleam.com> wrote:
> 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.
Thanks for the extra eyes, slightly more awake now and it's
coherent :)
Pushed as commit ee9d839a137ad4f735e77d6b9e01698c8391006e
Diff inlined anyways for solver SEO:
diff --git a/README b/README
index a3c1e61c..2412e40f 100644
--- a/README
+++ b/README
@@ -14,7 +14,8 @@ public-inbox spawned around three main ideas:
use of non-Free services or software.
* Graphical user interfaces should not be required for text-based
- communication.
+ communication. Users may have broken graphics drivers, limited
+ eyesight, or unable to afford modern hardware.
public-inbox aims to be easy-to-deploy and manage; encouraging projects
to run their own instances with minimal overhead.
next prev parent reply other threads:[~2020-04-01 23:40 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
2020-04-01 23:40 ` Eric Wong [this message]
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=20200401234054.GA32225@dcvr \
--to=e@yhbt.net \
--cc=kyle@kyleam.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.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).