From: Will Senn <will.senn@gmail.com>
To: tuhs@tuhs.org, coff <coff@tuhs.org>
Subject: [TUHS] Re: move to COFF Re: Re: Proper use of TUHS (was Re: Typesetter C compiler)
Date: Fri, 3 Feb 2023 11:31:44 -0600 [thread overview]
Message-ID: <5000bf66-4ae0-710f-c613-3bed61fb5f91@gmail.com> (raw)
In-Reply-To: <057be760-5f24-6274-c4b4-97ee8c439615@gmail.com>
Oh, and of course I would cc the old address!
Reply on the correct COFF address <coff@tuhs.org>
Sheesh.
On 2/3/23 11:26 AM, Will Senn wrote:
> We're in COFF territory again. I am enjoying the conversation, but
> let's self monitor. Perhaps, a workflow for this is that when we drift
> off into non-unix history discussion, we cc: COFF and tell folks to
> continue there? As a test I cced it on this email, don't reply all to
> this list. Just let's talk about it over in coff. If you aren't on
> coff join it.
>
> If you aren't sure or think most folks on the list want to discuss it.
> Post it on COFF, if you don't get any traction, reference the COFF
> thread and tease it in TUHS.
>
> This isn't at all a gripe - I heart all of our discussions, but I
> agree that it's hard to keep it history related here with no outlet
> for tangential discussion - so, let's put coff to good use and try it
> for those related, but not quite discussions.
>
> Remember, don't reply to TUHS on this email :)!
>
> - will
>
> On 2/3/23 11:11 AM, Steve Nickolas wrote:
>> On Fri, 3 Feb 2023, Larry McVoy wrote:
>>
>>> Some things will never go away, like keep your fingers off of my L1
>>> cache lines. I think it's mostly lost because of huge memories, but
>>> one of the things I love about early Unix is how small everything was.
>>> Most people don't care, but if you want to go really fast, there is no
>>> replacement for small.
>>>
>>> Personally, I'm fine with some amount of "list about new systems where
>>> we can ask about history because that helps us build those new
>>> systems".
>>> Might be just me, I love systems discussions.
>>
>> I find a lot of my own stuff is like this - kindasorta fits and
>> kindasorta doesn't for similar reasons.
>>
>> (Since a lot of what I've been doing lately is creating a
>> SysV-flavored rewrite of Unix from my own perspective as a
>> 40-something who actually got most of my experience coding for
>> 16-bits and MS-DOS, and speaks fluent but non-native C. I'm sure it
>> comes out in my coding style.)
>>
>> -uso.
>
next prev parent reply other threads:[~2023-02-03 17:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 19:02 [TUHS] Typesetter C compiler Noel Chiappa
2023-02-02 21:57 ` [TUHS] " Jonathan Gray
2023-02-03 0:43 ` Jonathan Gray
2023-02-02 22:36 ` [TUHS] Proper use of TUHS (was Re: Typesetter C compiler) Dan Cross
2023-02-02 22:41 ` [TUHS] " Larry McVoy
2023-02-02 22:47 ` Jim Capp
2023-02-03 1:44 ` Dave Horsfall
2023-02-03 13:17 ` Alan D. Salewski
2023-02-03 13:55 ` Larry McVoy
2023-02-06 20:02 ` Chris Hanson
2023-02-03 14:11 ` Chet Ramey
2023-02-03 14:15 ` Larry McVoy
2023-02-03 16:39 ` Dan Cross
2023-02-03 16:54 ` Larry McVoy
2023-02-03 17:08 ` Dan Cross
2023-02-03 17:11 ` Steve Nickolas
2023-02-03 17:26 ` [TUHS] move to COFF " Will Senn
2023-02-03 17:31 ` Will Senn [this message]
2023-02-03 17:45 ` [TUHS] " Bakul Shah
2023-02-05 10:42 ` steve jenkin
2023-02-04 8:03 ` [TUHS] A List for New Systems Influenced by History. (Was: Proper use of TUHS) Ralph Corderoy
2023-02-04 13:56 ` [TUHS] " Larry McVoy
2023-02-04 17:31 ` [TUHS] Re: A List for New Systems Influenced by History Angel M Alganza
2023-02-03 6:36 ` [TUHS] Re: Proper use of TUHS (was Re: Typesetter C compiler) Lars Brinkhoff
2023-02-04 22:38 ` Tomasz Rola
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=5000bf66-4ae0-710f-c613-3bed61fb5f91@gmail.com \
--to=will.senn@gmail.com \
--cc=coff@tuhs.org \
--cc=tuhs@tuhs.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 NNTP newsgroup(s).