Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #228919
| From | <tomas@tuxteam.de> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Hijacking Threads [was: Re: rsync link corruption with -H and --link-dest] |
| Date | 2020-11-22 18:30 +0100 |
| Message-ID | <Be1lv-3wT-1@gated-at.bofh.it> (permalink) |
| References | <Be0fM-2UE-3@gated-at.bofh.it> <Be0Su-37V-13@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Sun, Nov 22, 2020 at 04:55:19PM +0000, Gareth Evans wrote: [...] > Thanks to all who have replied pointing out the issues. No worries. Things happen. No need to defend yourself, I hope. > In my defence, I don't use conversation view in general (so lack experience) and had imagined Fastmail's documented approach (for its webmail and app) to be standards-based: > > "Conversations get split apart and form new conversation threads when: > > 1. The subject changes > This usually means a new topic is being discussed so a new conversation thread is formed. > [...]" Yeah. That's, sadly, something Outlook inflicted on us. > https://www.fastmail.com/help/receive/conversations.html > > I now realise this is at odds with the relevant standards (and eg. Thunderbird's approach): > > https://en.wikipedia.org/wiki/Conversation_threading > > Anyway, apologies. It'd on me to apologise should I have created bad feelings. This mailing list is a big marketplace, and trying to point out conventions which help to keep communication easy is something I do from time to time. I try to convey things without being hurtful -- just tell me whenever I fail at that :) Cheers -- t
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: Hijacking Threads [was: Re: rsync link corruption with -H and --link-dest] Brad Rogers <brad@fineby.me.uk> - 2020-11-22 17:20 +0100
Re: Hijacking Threads [was: Re: rsync link corruption with -H and --link-dest] "Gareth Evans" <donotspam@fastmail.fm> - 2020-11-22 18:00 +0100
Re: Hijacking Threads [was: Re: rsync link corruption with -H and --link-dest] <tomas@tuxteam.de> - 2020-11-22 18:30 +0100
Re: Hijacking Threads [was: Re: rsync link corruption with -H and --link-dest] "Gareth Evans" <donotspam@fastmail.fm> - 2020-11-22 18:40 +0100
Re: Hijacking Threads [was: Re: rsync link corruption with -H and --link-dest] Brad Rogers <brad@fineby.me.uk> - 2020-11-22 18:30 +0100
Re: Hijacking Threads [was: Re: rsync link corruption with -H and --link-dest] "Gareth Evans" <donotspam@fastmail.fm> - 2020-11-22 18:40 +0100
Re: Hijacking Threads [was: Re: rsync link corruption with -H and --link-dest] Brad Rogers <brad@fineby.me.uk> - 2020-11-22 19:00 +0100
Re: Hijacking Threads [was: Re: rsync link corruption with -H and --link-dest] Celejar <celejar@gmail.com> - 2020-11-22 23:50 +0100
Re: Hijacking Threads [was: Re: rsync link corruption with -H and --link-dest] "Gareth Evans" <garethevans@fastmail.fm> - 2020-11-22 18:50 +0100
Re: Hijacking Threads [was: Re: rsync link corruption with -H and --link-dest] Charles Curley <charlescurley@charlescurley.com> - 2020-11-22 20:10 +0100
Re: Hijacking Threads [was: Re: rsync link corruption with -H and --link-dest] Brad Rogers <brad@fineby.me.uk> - 2020-11-22 20:20 +0100
Re: Hijacking Threads [was: Re: rsync link corruption with -H and --link-dest] Celejar <celejar@gmail.com> - 2020-11-23 17:20 +0100
Re: Hijacking Threads [was: Re: rsync link corruption with -H and --link-dest] Brad Rogers <brad@fineby.me.uk> - 2020-11-23 23:20 +0100
Re: Hijacking Threads [was: Re: rsync link corruption with -H and --link-dest] "Jeremy Nicoll" <jn.ml.dbn.25@letterboxes.org> - 2020-11-23 20:50 +0100
csiph-web