[TUHS] Puzzled about COFF

[TUHS] Puzzled about COFF

[Douglas McIlroy]

[-- Attachment #1: Type: text/plain, Size: 266 bytes --]

I subscribe to the TUHS mailing list, delivered in digest form. I do not
remember having subscribed to COFF, and am not aware of how to do so. Yet
COFF messges come in my TUHS digest. How does COFF differ from TUHS and how
does one subscibe to it (if at all)?

Doug

[-- Attachment #2: Type: text/html, Size: 312 bytes --]

[TUHS] Re: Puzzled about COFF

[Dan Cross]

On Thu, Jul 11, 2024 at 9:59 AM Douglas McIlroy
<douglas.mcilroy@dartmouth.edu> wrote:
> I subscribe to the TUHS mailing list, delivered in digest form. I do not remember having subscribed to COFF, and am not aware of how to do so. Yet COFF messges come in my TUHS digest. How does COFF differ from TUHS and how does one subscibe to it (if at all)?

Whereas TUHS is specific to Unix history, COFF (Computing
Old-Fashioned Facts---not the real acronym, but one I just made up,
I'm afraid) is more general. When a thread veers too far from Unix
history for TUHS, it will often be redirected to COFF; a way to do
this is to send a followup message, addressing TUHS in the Bcc: header
(to let folks know it's moving) and directly Cc: COFF, which is
possibly why one may see the occasional COFF message, despite not
being subscribed.

I believe that Warren subscribes people manually to both lists.

        - Dan C.

[TUHS] Re: Puzzled about COFF

[Clem Cole]

[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]

Doug,


On Thu, Jul 11, 2024 at 9:59 AM Douglas McIlroy <
douglas.mcilroy@dartmouth.edu> wrote:

> I subscribe to the TUHS mailing list, delivered in digest form. I do not
> remember having subscribed to COFF,
>

https://www.tuhs.org/cgi-bin/mailman/listinfo/coff

Although I believe when it was first set up, Warren asked people on TUHS to
send him a note.




> and am not aware of how to do so. Yet COFF messges come in my TUHS digest.
>
When things move from TUHS to COFF - two things (sometimes) occur.  The
person moving it, should BCC: TUHS and mention that it's moving, but .. all
preceding message will not yet have COFF in the header and thus will
continue to send things to TUHS.



> How does COFF differ from TUHS and how does one subscibe to it (if at all)?
>
As you know, many of these streams often diverge to non-UNIX-related issues.
Warren created COFF as a place to have those discussions, but people who
only wanted to discuss items relevant to the UNIX community should stick to
its history.
ᐧ
ᐧ
ᐧ

[-- Attachment #2: Type: text/html, Size: 3626 bytes --]

[TUHS] Re: Puzzled about COFF

[Theodore Ts'o]

On Thu, Jul 11, 2024 at 09:59:28AM -0400, Douglas McIlroy wrote:
> I subscribe to the TUHS mailing list, delivered in digest form. I do not
> remember having subscribed to COFF, and am not aware of how to do so. Yet
> COFF messges come in my TUHS digest. How does COFF differ from TUHS and how
> does one subscibe to it (if at all)?

What sometimes happen is that a message will be sent to both the COFF
and TUHS lists, and then when someone replies, you'll still see [COFF]
in the subject line.

As Clem mentioned on another thread with the same question, best
practice when moving a thread which is no longer on-topic with
Unix/TUHS (e.g., when westart talking about Mainframes, VMS, et. al)
is to Bcc: TUHS saying that you are moving the discussion to COFF.
That's because if you use CC, then when someone responds, it replies
go to both list, instead of moving the discussion from one list to
another.

						- Ted

[TUHS] Re: Puzzled about COFF

[Paul Winalski]

[-- Attachment #1: Type: text/plain, Size: 906 bytes --]

On Thu, Jul 11, 2024 at 11:26 AM Theodore Ts'o <tytso@mit.edu> wrote:

> As Clem mentioned on another thread with the same question, best
> practice when moving a thread which is no longer on-topic with
> Unix/TUHS (e.g., when westart talking about Mainframes, VMS, et. al)
> is to Bcc: TUHS saying that you are moving the discussion to COFF.
> That's because if you use CC, then when someone responds, it replies
> go to both list, instead of moving the discussion from one list to
> another.
>

You can blame me for the recent spate of messages intended for COFF going
also to TUHS.  The thread on instruction set emulation/translation had
moved far off-topic for TUHS so I sent my reply to COFF, copying TUHS on
the message announcing the transfer of the topic.  But I used CC, not BCC,
so some further replies in the thread went to both lists.

Sorry about that, Chief!

-Paul W.

[-- Attachment #2: Type: text/html, Size: 1238 bytes --]

[TUHS] Re: Puzzled about COFF

[Grant Taylor via TUHS]

On 7/11/24 11:56 AM, Paul Winalski wrote:
> You can blame me for the recent spate of messages intended for COFF 
> going also to TUHS.  The thread on instruction set emulation/translation 
> had moved far off-topic for TUHS so I sent my reply to COFF, copying 
> TUHS on the message announcing the transfer of the topic.  But I used 
> CC, not BCC, so some further replies in the thread went to both lists.

I wonder if we could leverage some technology to help us.

Specifically I wonder if we can cause Mailman to moderate messages to 
TUHS that are also CCed to COFF.

While we're asking Mailman to do things, I wonder if we can have it 
remove TUHS from headers (From: and Reply-To:) from messages going to COFF.

Hopefully this would steer messages a little bit.



-- 
Grant. . . .
unix || die