Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Diego Calleja <diegocg@gmail.com>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: linux-btrfs@vger.kernel.org, Hugo Mills <hugo@carfax.org.uk>
Subject: Re: [PATCH 0/5] [RFC] RAID-level terminology change
Date: Mon, 11 Mar 2013 00:06:51 +0100	[thread overview]
Message-ID: <1602186.jds4Ur0UDu@diego-arch> (raw)
In-Reply-To: <201303101223.56805.Martin@lichtvoll.de>

El Domingo, 10 de marzo de 2013 12:23:56 Martin Steigerwald escribió:
> Any other idea to make it less cryptic?

I would vote for optionally allowing to expand the codes into
something more verbose and self-documented, ie:

1CmS1P <-> 1Copy-manyStripes-1Parity

  parent reply	other threads:[~2013-03-10 23:11 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-09 20:31 [PATCH 0/5] [RFC] RAID-level terminology change Hugo Mills
2013-03-09 20:31 ` [PATCH 1/5] Use nCmSpP format for mkfs Hugo Mills
2013-03-09 20:31 ` [PATCH 2/5] Move parse_profile to utils.c Hugo Mills
2013-03-09 20:31 ` [PATCH 3/5] Convert balance filter parser to use common nCmSpP replication-level parser Hugo Mills
2013-03-09 20:31 ` [PATCH 4/5] Change output of btrfs fi df to report new (or old) RAID names Hugo Mills
2013-03-09 20:31 ` [PATCH 5/5] Add man page description for nCmSpP replication levels Hugo Mills
2013-03-10 14:01   ` Goffredo Baroncelli
2013-03-10 17:20     ` Hugo Mills
2013-03-10 17:52       ` Goffredo Baroncelli
2013-03-09 21:38 ` [PATCH 0/5] [RFC] RAID-level terminology change Harald Glatt
     [not found] ` <CAFWF=am4ki529Zez4123gYk3BD+Z9RONRpAK7NZe=skHzcdMiw@mail.gmail.com>
2013-03-09 21:46   ` Hugo Mills
2013-03-09 22:25 ` Roger Binns
2013-03-10  1:44   ` Hugo Mills
2013-03-10  5:41     ` Roger Binns
2013-03-10  6:29       ` Harald Glatt
2013-03-10  6:37         ` Harald Glatt
2013-03-10 11:31           ` Martin Steigerwald
2013-03-10 11:48           ` Roger Binns
2013-03-10 22:04       ` Hugo Mills
2013-03-11  0:21         ` Roger Binns
2013-03-27  4:27           ` Brendan Hide
2013-03-27  5:24             ` Roger Binns
2013-03-10 11:23 ` Martin Steigerwald
2013-03-10 14:11   ` Goffredo Baroncelli
2013-03-10 21:36   ` Hugo Mills
2013-03-10 21:45     ` Harald Glatt
2013-03-10 22:59       ` Goffredo Baroncelli
2013-03-10 22:06         ` Harald Glatt
2013-03-10 23:06   ` Diego Calleja [this message]
2013-03-10 15:43 ` Goffredo Baroncelli
2013-03-10 22:24   ` Hugo Mills
2013-03-10 22:42     ` Harald Glatt
2013-03-10 23:40   ` sam tygier
2013-03-10 23:49     ` Hugo Mills
2013-03-11 14:14       ` David Sterba
2013-03-10 23:55 ` sam tygier
2013-03-11  8:56   ` Hugo Mills

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=1602186.jds4Ur0UDu@diego-arch \
    --to=diegocg@gmail.com \
    --cc=Martin@lichtvoll.de \
    --cc=hugo@carfax.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox