linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adam Borowski <kilobyte@angband.pl>
To: Stefan Malte Schumacher <stefan.m.schumacher@gmail.com>
Cc: Nicholas Steeves <nsteeves@gmail.com>,
	Chris Murphy <lists@colorremedies.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Size of scrubbed Data
Date: Sat, 17 Sep 2016 15:27:23 +0200	[thread overview]
Message-ID: <20160917132723.GA27654@angband.pl> (raw)
In-Reply-To: <CAA3ktqm0eSm3bM5cKsa1D-rnELTQ83rPkH-QFfEmfuBV1ZMe9A@mail.gmail.com>

On Sat, Sep 17, 2016 at 01:02:18PM +0200, Stefan Malte Schumacher wrote:
> Concerning Testing: I only use it on desktops and home servers, which
> do not offer any services to the net. I am very fond of Debian and
> always use stable or even old-stable on work servers, but was finally
> to annoyed at the fact that the software I was using on a fresh
> installation was practically already out of date.

These days *-backports has pretty much everything you'd want for a real
reason, and maintainers tend to be forthcoming when asked; the rules allow
anyone with upload rights to backport anything (the string attached is
"you're then responsible for bugs and other problems") but it's customary to
ask the regular maintainer first.

Of course you won't get bling this way -- it's unreasonable to backport more
than a few dependant packages so a desktop environment is right out.  But
server packages, a major new version of an editor or mail client, or
sometimes even a new game are fine.

Obviously, stuff like new kernels or new btrfs-progs tend to come fast.

On the other hand, this means using testing outside of (soft-) freezes
became far less supported than it used to be in the past.

-- 
Second "wet cat laying down on a powered-on box-less SoC on the desk" close
shave in a week.  Protect your ARMs, folks!

  reply	other threads:[~2016-09-17 13:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-15 15:48 Size of scrubbed Data Stefan Malte Schumacher
2016-09-15 20:11 ` g6094199
2016-09-15 21:10   ` Stefan Malte Schumacher
2016-09-15 21:18 ` Chris Murphy
2016-09-16 12:21   ` Nicholas Steeves
2016-09-17 11:02     ` Stefan Malte Schumacher
2016-09-17 13:27       ` Adam Borowski [this message]
2016-09-17 14:34   ` Tim Walberg
2016-09-17 15:08     ` Tim Walberg
2016-09-17 15:24     ` Chris Murphy

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=20160917132723.GA27654@angband.pl \
    --to=kilobyte@angband.pl \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=nsteeves@gmail.com \
    --cc=stefan.m.schumacher@gmail.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).