From: Chris Murphy <lists@colorremedies.com>
To: Marc Haber <mh+linux-btrfs@zugschlus.de>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: balance hangs and starts again on reboot
Date: Sat, 5 Mar 2016 10:07:03 -0700 [thread overview]
Message-ID: <CAJCQCtQoad6dGUHnk5UMJzYMOcmZiVbJoQ_1o9nqZTm-xOQ+1g@mail.gmail.com> (raw)
In-Reply-To: <20160305141232.GB1902@torres.zugschlus.de>
On Sat, Mar 5, 2016 at 7:12 AM, Marc Haber <mh+linux-btrfs@zugschlus.de> wrote:
> What is the most helpful way to include logs?
Attach as a text file. If they're too big and get rejected, then it
depends. If I'm pretty sure it's a bug, I open a bug report on
bugzilla.kernel.org and attach there, then URL in list. If I'm not
sure, I put the text file on google drive or dropbox and post public
URL here.
> including them
> causes "annoying MUA wrapping".
It can be either sending or receiving client that does this. I have no
doubt gmail does it sending and receiving because I always have this
problem.
> I do only have 24 years of e-mail
> experience, so I'm a clueless newbie, maybe one can give advice how to
> do that properly.
I've given up with pasting kernel messages inline.
--
Chris Murphy
prev parent reply other threads:[~2016-03-05 17:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 17:31 balance hangs and starts again on reboot Marc Haber
2016-03-04 18:09 ` Holger Hoffstätte
2016-03-05 14:17 ` Marc Haber
2016-03-05 15:38 ` Holger Hoffstätte
2016-03-05 17:25 ` Marc Haber
2016-03-05 18:00 ` Holger Hoffstätte
2016-03-06 6:12 ` Duncan
2016-03-04 19:08 ` Chris Murphy
2016-03-05 14:12 ` Marc Haber
2016-03-05 17:07 ` Chris Murphy [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=CAJCQCtQoad6dGUHnk5UMJzYMOcmZiVbJoQ_1o9nqZTm-xOQ+1g@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mh+linux-btrfs@zugschlus.de \
/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).