From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Kernel 3.19 and still "disk full" even though 'btrfs fi df" reports enough room left?
Date: Fri, 20 Nov 2015 10:44:42 +0000 (UTC) [thread overview]
Message-ID: <pan$423ea$b2ebc24b$fe1c12ba$fb781f7e@cox.net> (raw)
In-Reply-To: 564EEA19.1000109@gmail.com
linux-btrfs.tebulin posted on Fri, 20 Nov 2015 10:38:33 +0100 as
excerpted:
> Am 20.11.2015 um 04:14 schrieb Duncan:
>> Meta-comment:
>>
>> Apparently that attribution should actually be to Hugo Mills. I've no
>> idea what went wrong, but at least here as received from gmane.org, the
>> from header really does say linux-btrfs.tebulin, so something obviously
>> bugged out somewhere!
>
> Meta-Answer: My fault
>
> I accidentally exposed my spamgourmet proxy address to Hugo by taking
> him CC. He replied to all assuming it would go directly to the list, but
> the proxy address masked his original address an put id in it.
>
> Sorry for messing up!
Makes sense.
While I suppose his reply to all went to the list and to the proxy, the
proxy bounced it, presumably with the same message-id, and anything that
tracks by message-id (including my client), which is supposed to be
unique and thus usable for message tracking, would see only one of the
two. Which one would depend on which one got to it first, and whether it
took that and refused the other one, or let the second one override the
first.
Either way, definitely confusing, but at least there's a reasonable
explanation now. Thanks for helping to clear that up! =:^)
(FWIW, as with most linux kernel lists, replying to all is customary. I
generally reply only to the list, however, because it's far easier with
my specific setup, tho I'll reply to author as well if specifically
requested. But Hugo actually does the list-recommended thing by replying
to all by default.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2015-11-20 10:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 18:53 Kernel 3.19 and still "disk full" even though 'btrfs fi df" reports enough room left? linux-btrfs.tebulin
2015-11-18 19:08 ` Hugo Mills
2015-11-19 0:42 ` Qu Wenruo
2015-11-19 2:16 ` Duncan
2015-11-20 11:39 ` Dmitry Katsubo
2015-11-20 13:21 ` Austin S Hemmelgarn
2015-11-20 13:27 ` Hugo Mills
2015-11-20 13:52 ` Austin S Hemmelgarn
2015-11-20 16:39 ` Dmitry Katsubo
2015-11-19 17:35 ` linux-btrfs.tebulin
2015-11-19 18:28 ` Hugo Mills
2015-11-19 18:45 ` linux-btrfs.tebulin
2015-11-19 18:56 ` linux-btrfs.tebulin
2015-11-19 19:26 ` linux-btrfs.tebulin
2015-11-20 3:14 ` Duncan
2015-11-20 9:38 ` linux-btrfs.tebulin
2015-11-20 10:44 ` Duncan [this message]
2015-11-20 14:25 ` Dmitry Katsubo
2015-11-19 20:18 ` Austin S Hemmelgarn
2015-11-19 5:58 ` Roman Mamedov
2015-11-19 8:31 ` Patrik Lundquist
2015-11-19 12:28 ` Austin S Hemmelgarn
2015-11-20 2:11 ` Duncan
2015-11-20 13:13 ` Austin S Hemmelgarn
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='pan$423ea$b2ebc24b$fe1c12ba$fb781f7e@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.