From: segaloco via TUHS <tuhs@tuhs.org>
To: Pete Turnbull <pete@dunnington.plus.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Reply-To and Mail-Followup-To (was: Re: UNIX System V Release 2.2 gdts Vax-780)
Date: Fri, 17 Mar 2023 15:33:24 +0000 [thread overview]
Message-ID: <WUANnjC1WBKIGtyvJoPO4mJzNWdLahY0oF7KHv9ojwAuzUnVYY8pGBeGGuVdWdJC9fpvu5dAERhKUsO7Vq9-TnSz1T-wNrAAG8Go2STgJMs=@protonmail.com> (raw)
In-Reply-To: <db1a8a93-edb3-e5e5-b17e-6b03d297e1b5@dunnington.plus.com>
I just hit whatever reply button I wind up hitting, usually reply all. End of the day, it's just words on a screen, if I have to skip past a few emails here and there due to random Cc lists, whatever, I'm not sorting physical junk mail, it all goes away when I turn off the screen.
- Matt G.
------- Original Message -------
On Friday, March 17th, 2023 at 8:12 AM, Pete Turnbull <pete@dunnington.plus.com> wrote:
> On 17/03/2023 03:30, G. Branden Robinson wrote:
>
> > At 2023-03-17T14:17:34+1100, Dave Horsfall wrote:
> >
> > > On Thu, 16 Mar 2023, G. Branden Robinson wrote:
> > >
> > > > [replying only to list]
> > >
> > > Short of replying to the sender alone, is there any other way to reply?
> >
> > Apparently there is; reply-all seems to have become the norm over the
>
>
> Thunderbird has Reply, Reply-All, and Reply-List. I'm sure you can
> guess which I'm using for this message.
>
> --
> Pete
> Pete Turnbull
next prev parent reply other threads:[~2023-03-17 15:33 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 11:59 [TUHS] Re: UNIX System V Release 2.2 gdts Vax-780 Noel Chiappa
2023-03-15 21:03 ` Warren Toomey via TUHS
2023-03-15 21:08 ` Clem Cole
2023-03-15 21:15 ` Luther Johnson
2023-03-15 21:18 ` Seth Morabito
2023-03-15 21:22 ` Larry McVoy
2023-03-15 21:27 ` Clem Cole
2023-03-15 21:38 ` KenUnix
2023-03-16 23:18 ` Clem Cole
2023-03-16 23:48 ` Charles H. Sauer (he/him)
2023-03-17 1:08 ` Steve Nickolas
2023-03-15 21:46 ` Steve Nickolas
2023-03-15 21:50 ` Luther Johnson
2023-03-15 21:56 ` steve jenkin
2023-03-15 22:15 ` Larry McVoy
2023-03-15 23:30 ` Warner Losh
2023-03-15 23:41 ` Luther Johnson
2023-03-16 0:29 ` Warner Losh
2023-03-16 0:36 ` Rich Salz
2023-03-16 1:55 ` G. Branden Robinson
2023-03-16 21:14 ` Dave Horsfall
2023-03-17 0:33 ` Rich Salz
2023-03-17 1:03 ` [TUHS] copyright (was: Re: UNIX System V Release 2.2 gdts Vax-780) G. Branden Robinson
2023-03-17 1:05 ` [TUHS] Re: UNIX System V Release 2.2 gdts Vax-780 segaloco via TUHS
2023-03-17 2:03 ` G. Branden Robinson
2023-03-17 3:17 ` Dave Horsfall
2023-03-17 3:30 ` [TUHS] Reply-To and Mail-Followup-To (was: Re: UNIX System V Release 2.2 gdts Vax-780) G. Branden Robinson
2023-03-17 15:12 ` [TUHS] " Pete Turnbull
2023-03-17 15:33 ` segaloco via TUHS [this message]
2023-03-17 16:42 ` Steve Nickolas
2023-03-17 18:27 ` Marc Donner
2023-03-16 1:15 ` [TUHS] Re: UNIX System V Release 2.2 gdts Vax-780 Larry McVoy
2023-03-16 2:14 ` Luther Johnson
2023-03-15 23:44 ` Brad Spencer
2023-03-16 4:37 ` Dave Horsfall
2023-03-15 23:56 ` [TUHS] Re: OSF/1.0 Sources Joseph Holsten
2023-03-17 2:28 ` [TUHS] Re: UNIX System V Warren Toomey via TUHS
2023-03-17 18:49 [TUHS] Re: Reply-To and Mail-Followup-To (was: Re: UNIX System V Release 2.2 gdts Vax-780) Norman Wilson
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='WUANnjC1WBKIGtyvJoPO4mJzNWdLahY0oF7KHv9ojwAuzUnVYY8pGBeGGuVdWdJC9fpvu5dAERhKUsO7Vq9-TnSz1T-wNrAAG8Go2STgJMs=@protonmail.com' \
--to=tuhs@tuhs.org \
--cc=pete@dunnington.plus.com \
--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).