From: Jeremy Baxter <jeremy@baxters.nz>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] intro.1: Improve wording in initial introduction
Date: Mon, 17 Jun 2024 11:38:06 +1200 [thread overview]
Message-ID: <87a5jk31cx.fsf@baxters.nz> (raw)
In-Reply-To: <h2n62rzdo3sska6dcjxpgkootmafjyq22nu75dw7js5ycjc7oc@wogudmcmgmg4> (Alejandro Colomar's message of "Mon, 17 Jun 2024 01:05:45 +0200")
Alejandro Colomar <alx@kernel.org> writes:
>> -Linux is a flavor of UNIX, and as a first approximation
>> -all user commands under UNIX work precisely the same under
>> -Linux (and FreeBSD and lots of other UNIX-like systems).
>> +Linux is a flavor of UNIX, and user commands under UNIX
>> +work similarly under Linux (and lots of other UNIX-like systems too,
>> +like FreeBSD).
>
> I like the changes in this paragraph, except for the removal of "as a
> first approximation". Not a big deal, though.
I don't hear "as a first approximation" spoken often and it just brings
more cognitive overhead to the content in my opinion.
>> -It is not built-in, but is just a program
>> -and you can change your shell.
>> -Everybody has their own favorite one.
>> +It is not built-in,
>> +but is just another program.
>
> I would maybe use a ';'?
>
> It is not built-in;
> it is just another program.
That's better, I'll use that in v2.
> I think I'll apply this patch. Let me meditate it to-night. I CCed
> Doug, in case he has any comments (it would be great to hear his
> feedback).
>
> Have a lovely night!
> Alex
Sweet, thanks for the review.
prev parent reply other threads:[~2024-06-16 23:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-16 22:29 [PATCH] intro.1: Improve wording in initial introduction Jeremy Baxter
2024-06-16 23:05 ` Alejandro Colomar
2024-06-16 23:38 ` Jeremy Baxter [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=87a5jk31cx.fsf@baxters.nz \
--to=jeremy@baxters.nz \
--cc=alx@kernel.org \
--cc=linux-man@vger.kernel.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