From: Joseph Fannin <jfannin@gmail.com>
To: Andrew Buehler <abuehler.kernel@gmail.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Oliver Pinter <oliver.pntr@gmail.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Greg KH <greg@kroah.com>,
linux-scsi@vger.kernel.org, linux-usb@vger.kernel.org
Subject: [OT] GMail (was USB regression (and other failures)...)
Date: Sat, 16 Feb 2008 23:10:53 -0500 [thread overview]
Message-ID: <20080217041052.GA32381@nineveh.local> (raw)
In-Reply-To: <47B78A08.1020502@gmail.com>
On Sat, Feb 16, 2008 at 08:12:40PM -0500, Andrew Buehler wrote:
> [...] and I would not be in the least surprised if this turned out to
> be yet one more problem with gmail
It is; Gmail will refuse to POP more than one copy of a mail to you,
no matter how many copies it recieves via different paths. Which copy
you get seems to be dependant on which arrives first, so you can't
even hope a mail exchange will consistently arrive in one mailbox or
another.
Note that this also applies to mails cross-posted to multiple lists
you maybe be suscribed to; this breaks threading fantastically.
Google is aware of the issue, and considers it a feature. If you find
another free mail service which isn't so broken, I'd love to hear
about it.
---
That said, netiquette on the kernel lists is to *never* drop CC's.
Too much traffic crosses the lists for anyone to read it all and note
anything they might be interested and/or implicated in. Never
dropping CC's allows busy people to keep track of conversations
they've taken part in or that someone thinks they should see
without the worry of missing any important parts of one.
Or at least it does if your mail system isn't broken. We get what we
pay for. :-/
--
Joseph Fannin
jfannin@gmail.com
next prev parent reply other threads:[~2008-02-17 4:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 21:45 USB regression (and other failures) in 2.6.2[45]* Andrew Buehler
2008-02-16 14:32 ` Oliver Pinter
2008-02-16 15:20 ` Alan Stern
2008-02-16 16:46 ` Andrew Buehler
2008-02-16 17:16 ` Alan Stern
2008-02-16 21:33 ` Andrew Buehler
2008-02-16 23:11 ` Alan Stern
2008-02-17 1:12 ` Andrew Buehler
2008-02-17 3:35 ` Alan Stern
2008-02-17 16:21 ` Andrew Buehler
2008-02-19 20:35 ` USB regression (and other failures) in 2.6.2[45]* - mostly resolved Andrew Buehler
2008-02-20 15:50 ` Alan Stern
2008-02-20 17:06 ` Andrew Buehler
2008-02-20 17:15 ` Alan Stern
2008-02-20 18:27 ` Andrew Buehler
2008-02-20 19:29 ` Alan Stern
2008-02-21 16:05 ` Andrew Buehler
2008-02-21 16:36 ` Alan Stern
2008-02-21 17:17 ` Greg KH
2008-02-21 19:43 ` Andrew Buehler
2008-02-21 20:02 ` Alan Stern
2008-02-17 4:10 ` Joseph Fannin [this message]
2008-02-17 10:55 ` USB regression (and other failures) in 2.6.2[45]* Sergey Vlasov
2008-02-17 7:20 ` Paul Jackson
2008-02-17 16:17 ` Andrew Buehler
2008-02-17 16:20 ` Paul Jackson
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=20080217041052.GA32381@nineveh.local \
--to=jfannin@gmail.com \
--cc=abuehler.kernel@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver.pntr@gmail.com \
--cc=stern@rowland.harvard.edu \
/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