From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Expected behavior of bad sectors on one drive in a RAID1
Date: Wed, 21 Oct 2015 13:28:55 -0400 [thread overview]
Message-ID: <5627CB57.5030006@gmail.com> (raw)
In-Reply-To: <CAJCQCtTvbeJPfLQn0DWzXbUD+63q19efd2Rm29ePqA-W1j_fMg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1617 bytes --]
On 2015-10-21 12:01, Chris Murphy wrote:
> On Wed, Oct 21, 2015 at 2:07 PM, Austin S Hemmelgarn
> <ahferroin7@gmail.com> wrote:
>> And I realize of course right after sending this that my other reply didn't
>> get through because GMail refuses to send mail in plain text, no matter how
>> hard I beat it over the head...
>
> In the web browser version, to the right of the trash can for an email
> being written, there is an arrow with a drop down menu that includes
> "plain text mode" option which will work. This is often sticky, but
> randomly with the btrfs list the replies won't have this option
> checked and then they bounce. It's annoying. And then both the Gmail
> and Inbox Android apps have no such option so it's not possible reply
> to list emails from a mobile device short of changing mail clients
> just for this purpose.
I actually didn't know about the option in the drop down menu in the
Web-UI, although that wouldn't have been particularly relevant in this
case as I was replying from my phone. What's really annoying in that
case is that the 'Reply Inline' option makes things _look_ like they're
plain text, but they really aren't.
I've considered getting a different mail app, but for some reason the
only one I can find for Android that supports plain text e-mail is K-9
Mail, and I'm not too fond of the UI for that, and it takes way more
effort to set up than I'm willing to put in for something I almost never
use anyway (that and it doesn't (AFAICT) support S/MIME or Hashcash,
although GMail doesn't either, so that one's not a show stopper).
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
next prev parent reply other threads:[~2015-10-21 17:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 4:16 Expected behavior of bad sectors on one drive in a RAID1 james harvey
2015-10-20 4:45 ` Russell Coker
2015-10-20 13:00 ` Austin S Hemmelgarn
2015-10-20 13:15 ` Russell Coker
2015-10-20 13:59 ` Austin S Hemmelgarn
2015-10-20 19:20 ` Duncan
2015-10-20 19:59 ` Austin S Hemmelgarn
2015-10-20 20:54 ` Tim Walberg
2015-10-21 11:51 ` Austin S Hemmelgarn
2015-10-21 12:07 ` Austin S Hemmelgarn
2015-10-21 16:01 ` Chris Murphy
2015-10-21 17:28 ` Austin S Hemmelgarn [this message]
2015-10-20 18:54 ` Duncan
2015-10-20 19:48 ` Austin S Hemmelgarn
2015-10-20 21:24 ` Duncan
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=5627CB57.5030006@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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).