From: Dan Cross <crossd@gmail.com>
To: chet.ramey@case.edu
Cc: segaloco <segaloco@protonmail.com>, COFF <coff@tuhs.org>
Subject: [COFF] Re: [TUHS] Re: Generational development [was Re: Re: Early GUI on Linux]
Date: Tue, 28 Feb 2023 10:25:04 -0500 [thread overview]
Message-ID: <CAEoi9W5d0pgjEqkvkq4thOWB3oYnP1mSXfB7dNH+wHHw0s=E6Q@mail.gmail.com> (raw)
In-Reply-To: <708986db-d22e-3b1b-7dad-c15025697e42@case.edu>
On Tue, Feb 28, 2023 at 9:53 AM Chet Ramey <chet.ramey@case.edu> wrote:
> On 2/27/23 7:28 PM, Dan Cross wrote:
> > Huh? Rustup is the context that this came up in:
>
> I think if you look back in the thread, you'll find that the message from
> segaloco was a reply to a message of mine where I criticized the practice
> of piping from `wget' to `sh'. That's the context.
Yes, it is quite clear we were speaking past one another.
- Dan C.
next prev parent reply other threads:[~2023-02-28 15:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16241ceb-fe92-7f25-bda0-0b327847728d@case.edu>
[not found] ` <B7F6403D-E276-490B-AB11-835141F31339@iitbombay.org>
[not found] ` <vNaSB1ygm5HY-rV-WScmTmerF0acmZicvrUsW4kpDQ-n0-rpXSNQTh9V6mMHVLEbH6cjpXIQrHM8U4Oc4e6vzzA1sGF2eM9lxXqUbEn2bfc=@protonmail.com>
[not found] ` <735c811e-62ce-5384-b83f-a3887baac89d@case.edu>
2023-02-27 21:22 ` Dan Cross
2023-02-27 21:42 ` Chet Ramey
2023-02-27 22:01 ` Dan Cross
2023-02-27 23:23 ` Chet Ramey
2023-02-27 23:42 ` Larry McVoy
2023-02-28 0:29 ` Dan Cross
2023-02-28 0:28 ` Dan Cross
2023-02-28 14:53 ` Chet Ramey
2023-02-28 15:25 ` Dan Cross [this message]
2023-02-28 16:03 ` Chet Ramey
[not found] ` <8A7D978F-88A0-491D-90A3-A1CE843B3698@me.com>
2023-02-27 22:07 ` [COFF] Re: [TUHS] " Dan Cross
[not found] ` <CAJXSPs-1-3wrt_suJ9S3u0z_E6qAEpUUZ1Zk2oANXF6NQL9tDg@mail.gmail.com>
2023-02-27 22:17 ` [COFF] Re: [TUHS] " Dan Cross
2023-02-27 23:20 ` Stuff Received
[not found] <58626A0B-EF9C-4920-8E20-CE0C4210BA6A@planet.nl>
[not found] ` <Y/rGop0y22X9Dcxd@mit.edu>
[not found] ` <A3308FD9-F130-48BA-903A-4F7AA6CF2CC3@planet.nl>
[not found] ` <202302272004.31RK4aGG001510@freefriends.org>
[not found] ` <2f6faeb4-5e73-cf18-b0ff-edc3e1658f72@case.edu>
[not found] ` <202302272022.31RKMG2L004091@freefriends.org>
[not found] ` <CqEehkxsT6R2Pn65gn4t2uSN_AvnhjMP8HQDdZDPazLs9B4gZQ3R7BCd0Ko4EzbTwIm3n9FfTuaf1xBZKeEmwPoTutaIFv9juCO_3HoG5vg=@protonmail.com>
2023-02-27 21:04 ` Dan Cross
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='CAEoi9W5d0pgjEqkvkq4thOWB3oYnP1mSXfB7dNH+wHHw0s=E6Q@mail.gmail.com' \
--to=crossd@gmail.com \
--cc=chet.ramey@case.edu \
--cc=coff@tuhs.org \
--cc=segaloco@protonmail.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 NNTP newsgroup(s).