From: Chris Mason <mason@suse.com>
To: Oleg Drokin <green@namesys.com>
Cc: marcelo@conectiva.com.br, linux-kernel@vger.kernel.org,
reiserfs-dev@namesys.com, adilger@turbolabs.com
Subject: Re: [reiserfs-dev] [PATCH] UUID & volume labels support for reiserfs
Date: Wed, 09 Jan 2002 11:07:29 -0500 [thread overview]
Message-ID: <100150000.1010592449@tiny> (raw)
In-Reply-To: <20020109185826.A1680@namesys.com>
In-Reply-To: <20020109155504.A4551@namesys.com> <52160000.1010591279@tiny> <20020109185826.A1680@namesys.com>
On Wednesday, January 09, 2002 06:58:26 PM +0300 Oleg Drokin
<green@namesys.com> wrote:
> Hello!
>
> On Wed, Jan 09, 2002 at 10:47:59AM -0500, Chris Mason wrote:
>
>> > Attached is the patch that reserves space for volume label and UUID
>> > in reiserfs v3.6 superblock. It also generates random UUID for
>> > volumes converted from 3.5 to 3.6 format by the kernel. Original
>> > patch author is Andreas Dilger <adilger@turbolabs.com>. Please
>> > apply.
>> This should not be applied until an updated (non beta) reiserfsprogs
>> package that supports these features has been released.
> Hey, reserving some space in superblock won't hurt.
Reserving it is fine ;-) Using it isn't a good idea until the progs
understand it. Our policy should be to never require a progs update in a
stable kernel series (just like most stable parts of the kernel).
But, the progs are improving so quickly that we should bend this rule a
little bit. Another example is the unlink truncate patch never should have
been sent to Marcelo without a non-beta reiserfsprogs that understood it.
Neither should this patch (even though it is a much smaller problem).
-chris
next prev parent reply other threads:[~2002-01-09 16:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 12:55 [PATCH] UUID & volume labels support for reiserfs Oleg Drokin
2002-01-09 15:47 ` [reiserfs-dev] " Chris Mason
2002-01-09 15:58 ` Oleg Drokin
2002-01-09 16:07 ` Chris Mason [this message]
2002-01-09 16:25 ` Oleg Drokin
2002-01-09 16:38 ` Chris Mason
2002-01-09 16:44 ` Oleg Drokin
2002-01-09 17:14 ` Chris Mason
2002-01-11 9:23 ` Oleg Drokin
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=100150000.1010592449@tiny \
--to=mason@suse.com \
--cc=adilger@turbolabs.com \
--cc=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=reiserfs-dev@namesys.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