From: Marc MERLIN <marc@merlins.org>
To: Chris Murphy <lists@colorremedies.com>
Cc: Hugo Mills <hugo@carfax.org.uk>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: ext4 convert bugs, wiki warning?
Date: Mon, 3 Aug 2015 08:13:48 -0700 [thread overview]
Message-ID: <20150803151348.GS24824@merlins.org> (raw)
In-Reply-To: <CAJCQCtS46kodfTLo63pMdvD819xuo==5huc_E79kw4WYASiBdg@mail.gmail.com>
On Sat, Aug 01, 2015 at 02:48:41PM -0600, Chris Murphy wrote:
> On Sat, Aug 1, 2015 at 2:42 PM, Hugo Mills <hugo@carfax.org.uk> wrote:
> > On Sat, Aug 01, 2015 at 11:29:40AM -0600, Chris Murphy wrote:
> >> Does someone with wiki edit capability want to put up a warning about
> >> btrfs-convert problems? I don't think it needs to be a lengthy write
> >> up since the scope of the problem is not clear yet. But since there's
> >> definitely reproduced problems that have been going on for some time
> >> now maybe it'd be a good idea to put up a warning until this is more
> >> stable?
> >>
> >> I'm thinking of just a yellow warning "sidebar" like thing that maybe
> >> just says there's been a regression and it's breaking file systems,
> >> sometimes irreparably?
> >
> > You mean a warning like the very first sentence, in bold, that's
> > already on the wiki page?
> >
> > https://btrfs.wiki.kernel.org/index.php/Conversion_from_Ext3
>
> Doh!
I added that after the last thread.
You're welcome :)
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/
prev parent reply other threads:[~2015-08-03 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-01 17:29 ext4 convert bugs, wiki warning? Chris Murphy
2015-08-01 20:42 ` Hugo Mills
2015-08-01 20:48 ` Chris Murphy
2015-08-03 15:13 ` Marc MERLIN [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=20150803151348.GS24824@merlins.org \
--to=marc@merlins.org \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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 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.