From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>,
Omar Sandoval <osandov@osandov.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>,
Martin Raiber <martin@urbackup.org>
Subject: Re: strange No space left on device issues
Date: Fri, 21 Jul 2017 00:02:26 +0200 [thread overview]
Message-ID: <da04aa8b-175f-273b-3c05-f132094d3d68@mendix.com> (raw)
In-Reply-To: <1500587596.7266.20.camel@scientia.net>
On 07/20/2017 11:53 PM, Christoph Anton Mitterer wrote:
> On Thu, 2017-07-20 at 14:48 -0700, Omar Sandoval wrote:
> [...]
>
>>> I assume you'll take care to get that patch into stable kernels?
>>> Is this patch alone enough to recommend the Debian maintainers to
>>> include it into their 4.9 long term stable kernels?
>>
>> I'll mark it for stable, assuming Debian tracks the upstream LTS
>> releases it should get in.
+1 \o/
> Okay :-)
>
> Nevertheless I'll open a bug at their BTS, just to be safe.
The Debian kernel teams tries to minimize the amount of patches on top
of the original kernel code. Every patch added comes with a maintenance
burden.
So, the answer will probably be: Please get it in 4.9 itself.
--
Hans van Kranenburg
prev parent reply other threads:[~2017-07-20 22:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 14:39 strange No space left on device issues Christoph Anton Mitterer
2017-07-20 14:44 ` Christoph Anton Mitterer
[not found] ` <0102015d6083ffde-e6d15fd5-6e66-41a0-9ddf-af163c96ebd8-000000@eu-west-1.amazonses.com>
2017-07-20 15:20 ` Christoph Anton Mitterer
2017-07-20 15:20 ` Christoph Anton Mitterer
2017-07-20 17:32 ` Omar Sandoval
2017-07-20 17:48 ` Christoph Anton Mitterer
2017-07-20 17:55 ` Omar Sandoval
2017-07-20 18:06 ` Christoph Anton Mitterer
2017-07-20 18:14 ` Omar Sandoval
2017-07-20 20:28 ` Christoph Anton Mitterer
2017-07-20 21:19 ` Omar Sandoval
2017-07-20 21:33 ` Christoph Anton Mitterer
2017-07-20 21:48 ` Omar Sandoval
2017-07-20 21:53 ` Christoph Anton Mitterer
2017-07-20 21:59 ` Omar Sandoval
2017-07-20 22:02 ` Hans van Kranenburg [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=da04aa8b-175f-273b-3c05-f132094d3d68@mendix.com \
--to=hans.van.kranenburg@mendix.com \
--cc=calestyo@scientia.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=martin@urbackup.org \
--cc=osandov@osandov.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).