Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #229389
| From | Brad Rogers <brad@fineby.me.uk> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Replying |
| Date | 2020-12-06 15:40 +0100 |
| Message-ID | <Bj3mG-3ih-9@gated-at.bofh.it> (permalink) |
| References | (3 earlier) <BiMYy-1eM-11@gated-at.bofh.it> <BiWbv-729-1@gated-at.bofh.it> <BiYmZ-8uk-1@gated-at.bofh.it> <Bj0oP-1ix-19@gated-at.bofh.it> <Bj2Ai-2Lh-3@gated-at.bofh.it> |
| Organization | Catch 22 |
[Multipart message — attachments visible in raw view] - view raw
On Sun, 06 Dec 2020 15:42:49 +0200
Teemu Likonen <tlikonen@iki.fi> wrote:
Hello Teemu,
>It's not broken; it's perfectly valid and allowed.
My mistake; I didn't mean broken in the non-RFC compliant sense, but
broken in the sense of "Not what I want to take place". I set a
Reply-To because that's where I want the reply to go. If I want to take
things elsewhere, it's up to me to change headers used, etc. so the reply
goes to the correct place.
To *deliberately* not comply with somebody's request(1) is a failure(2).
One that will, in my little corner of the universe, land the perpetrator
in a kill-file. Failing to comply without adequate (in my view)
justification will land them in that kill-file a good deal sooner.
(1) So long as those wishes affect only the person(s) directly involved.
For example, should a request require ppl to top-post their replies to
posts on a list where interpolated posting is the norm and rightly, the
respondent should decline and, possibly, do their own kill-filing.
(2) Mistakes do happen, so I usually give people a couple of chances.
--
Regards _
/ ) "The blindingly obvious is
/ _)rad never immediately apparent"
It's becoming an obsession
Teenage Depression - Eddie & The Hot Rods
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
AMD GPU Sea Islands Problem Guyenne Tsui <guyenne@gmail.com> - 2020-12-05 15:30 +0100
Replying. [was Re: AMD GPU Sea Islands Problem] Charles Curley <charlescurley@charlescurley.com> - 2020-12-05 18:10 +0100
Re: Replying. [was Re: AMD GPU Sea Islands Problem] Kenneth Parker <sea7kenp@gmail.com> - 2020-12-05 18:30 +0100
Re: Replying. [was Re: AMD GPU Sea Islands Problem] Tixy <tixy@yxit.co.uk> - 2020-12-05 19:30 +0100
Re: Replying. [was Re: AMD GPU Sea Islands Problem] Charles Curley <charlescurley@charlescurley.com> - 2020-12-05 20:00 +0100
Re: Replying. [was Re: AMD GPU Sea Islands Problem] Andrei POPESCU <andreimpopescu@gmail.com> - 2020-12-05 22:10 +0100
Re: Replying. [was Re: AMD GPU Sea Islands Problem] rhkramer@gmail.com - 2020-12-05 23:50 +0100
Re: Replying. [was Re: AMD GPU Sea Islands Problem] Brad Rogers <brad@fineby.me.uk> - 2020-12-06 08:00 +0100
Re: Replying Teemu Likonen <tlikonen@iki.fi> - 2020-12-06 10:20 +0100
Re: Replying Brad Rogers <brad@fineby.me.uk> - 2020-12-06 12:30 +0100
Re: Replying rhkramer@gmail.com - 2020-12-06 13:10 +0100
Re: Replying Brad Rogers <brad@fineby.me.uk> - 2020-12-06 13:20 +0100
Re: Replying Teemu Likonen <tlikonen@iki.fi> - 2020-12-06 14:50 +0100
Re: Replying Brad Rogers <brad@fineby.me.uk> - 2020-12-06 15:40 +0100
Re: Replying Stefan Monnier <monnier@iro.umontreal.ca> - 2020-12-06 16:00 +0100
Re: Replying Brad Rogers <brad@fineby.me.uk> - 2020-12-06 20:00 +0100
Re: Replying Teemu Likonen <tlikonen@iki.fi> - 2020-12-06 21:50 +0100
Re: Replying Paul Johnson <baloo@ursamundi.org> - 2020-12-07 15:50 +0100
Re: Replying. [was Re: AMD GPU Sea Islands Problem] Celejar <celejar@gmail.com> - 2020-12-08 21:20 +0100
Re: Replying. [was Re: AMD GPU Sea Islands Problem] Charles Curley <charlescurley@charlescurley.com> - 2020-12-09 01:30 +0100
Re: Replying. [was Re: AMD GPU Sea Islands Problem] Celejar <celejar@gmail.com> - 2020-12-09 01:50 +0100
Re: Replying. [was Re: AMD GPU Sea Islands Problem] Charles Curley <charlescurley@charlescurley.com> - 2020-12-09 02:00 +0100
Re: Replying. [was Re: AMD GPU Sea Islands Problem] Celejar <celejar@gmail.com> - 2020-12-09 02:40 +0100
Re: Replying. [was Re: AMD GPU Sea Islands Problem] Brad Rogers <brad@fineby.me.uk> - 2020-12-09 09:20 +0100
Re: Replying. [was Re: AMD GPU Sea Islands Problem] Celejar <celejar@gmail.com> - 2020-12-09 19:20 +0100
Re: Replying. [was Re: AMD GPU Sea Islands Problem] Guyenne Tsui <guyenne@gmail.com> - 2020-12-11 21:20 +0100
Re: Replying. [was Re: AMD GPU Sea Islands Problem] Charles Curley <charlescurley@charlescurley.com> - 2020-12-11 22:10 +0100
Re: AMD GPU Sea Islands Problem Felix Miata <mrmazda@earthlink.net> - 2020-12-05 22:30 +0100
Re: AMD GPU Sea Islands Problem Guyenne Tsui <guyenne@gmail.com> - 2020-12-06 23:20 +0100
Re: AMD GPU Sea Islands Problem Felix Miata <mrmazda@earthlink.net> - 2020-12-11 23:20 +0100
Re: AMD GPU Sea Islands Problem Guyenne Tsui <guyenne@gmail.com> - 2020-12-12 17:30 +0100
Re: AMD GPU Sea Islands Problem Andrei POPESCU <andreimpopescu@gmail.com> - 2020-12-12 20:00 +0100
Re: AMD GPU Sea Islands Problem Guyenne Tsui <guyenne@gmail.com> - 2020-12-26 21:40 +0100
Re: AMD GPU Sea Islands Problem "Alexander V. Makartsev" <avbetev@gmail.com> - 2020-12-12 20:40 +0100
Re: AMD GPU Sea Islands Problem Guyenne Tsui <guyenne@gmail.com> - 2020-12-26 21:50 +0100
Re: AMD GPU Sea Islands Problem Felix Miata <mrmazda@earthlink.net> - 2020-12-13 00:50 +0100
Re: AMD GPU ^H^H^HSea Southern Islands Problem Felix Miata <mrmazda@earthlink.net> - 2020-12-13 01:00 +0100
csiph-web