linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: o1bigtenor <o1bigtenor@gmail.com>
To: Phil Turmel <philip@turmel.org>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Advice requested
Date: Tue, 3 Nov 2015 13:06:42 -0600	[thread overview]
Message-ID: <CAPpdf585CNw3DVsFpjYvwUjee43ShEbwf27-4yDGticmgxqPhQ@mail.gmail.com> (raw)
In-Reply-To: <5638F6AF.7020501@turmel.org>

On Tue, Nov 3, 2015 at 12:02 PM, Phil Turmel <philip@turmel.org> wrote:
> On 11/02/2015 10:41 AM, Phil Turmel wrote:
>> Good morning Dee,
>>
>> { Added linux-raid back -- convention on kernel.org is reply-to-all }
>
> The next exchange in this thread were too large to make it past the
> kernel.org size limits.  They contain all of the off-list traffic
> the Dee had in his archive and my responses to it.
>
> I've archived these two mails myself for public benefit -- they were
> intended to be public after all.
>
> http://www.turmel.org/other/Advice-requested-201511021821.eml
> http://www.turmel.org/other/Advice-requested-201511021943.eml
>
> There's a few lessons here:
>
> 1) Insist on staying on-list.  Dee's help drifted away when the
> problems weren't solved.  No-one else saw the traffic, so could
> not step in.
>
> 2) Trim replies. :-)  Good G*d, these were hard to read without
> missing details.
>
> 3) Persevere.
>

I do hope that someone finds the odyssey useful rather than just amusing
- - - its why I'm comfortable having all this public.

Dee

      reply	other threads:[~2015-11-03 19:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-31 11:55 Advice requested o1bigtenor
2015-11-01 20:55 ` Phil Turmel
     [not found]   ` <CAPpdf5_PUpR7GhBHUaQfWb8Q+7FZenxXgFqbaN3f3r0r6NQNDA@mail.gmail.com>
2015-11-02 15:41     ` Phil Turmel
     [not found]       ` <CAPpdf59MFX1oVwLC-bmQBaQp9K_9-+h0v64OGMnV1-k=eCzO0w@mail.gmail.com>
     [not found]         ` <5637BCE4.8000006@turmel.org>
2015-11-02 23:49           ` o1bigtenor
2015-11-03  0:11             ` Phil Turmel
2015-11-03  0:44               ` o1bigtenor
2015-11-03  0:57                 ` Phil Turmel
2015-11-03  1:02                   ` o1bigtenor
2015-11-03  1:55                     ` Phil Turmel
2015-11-03  4:03                       ` o1bigtenor
2015-11-03  4:09                         ` Phil Turmel
2015-11-03  4:28                           ` o1bigtenor
2015-11-03  4:47                             ` Phil Turmel
2015-11-03 12:45                               ` o1bigtenor
2015-11-03 13:09                                 ` Phil Turmel
2015-11-03 13:36                                   ` o1bigtenor
2015-11-03 15:49                                     ` Adam Goryachev
2015-11-03 16:08                                     ` Phil Turmel
     [not found]                                       ` <CAPpdf59o0kf1-mgB29AcgH2cpdwBrhazf3NeQUYNa6m9+c6C+A@mail.gmail.com>
2015-11-04  4:05                                         ` o1bigtenor
2015-11-04  4:31                                           ` Brad Campbell
2015-11-03 18:02       ` Phil Turmel
2015-11-03 19:06         ` o1bigtenor [this message]

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=CAPpdf585CNw3DVsFpjYvwUjee43ShEbwf27-4yDGticmgxqPhQ@mail.gmail.com \
    --to=o1bigtenor@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=philip@turmel.org \
    /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).