From: Oleg Drokin <green@namesys.com>
To: Chris Mason <mason@suse.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, 9 Jan 2002 19:25:26 +0300 [thread overview]
Message-ID: <20020109192526.A1732@namesys.com> (raw)
In-Reply-To: <20020109155504.A4551@namesys.com> <52160000.1010591279@tiny> <20020109185826.A1680@namesys.com> <100150000.1010592449@tiny>
In-Reply-To: <100150000.1010592449@tiny>
Hello!
On Wed, Jan 09, 2002 at 11:07:29AM -0500, Chris Mason wrote:
> >> 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
So we did it (reserved) ;)
We do not use it. (generating of UUID does not count)
> 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).
We do not require progs upadte. But if someone will update their progs voluntarily,
we cannot forbit them to! ;))
> Neither should this patch (even though it is a much smaller problem).
You just said that reserving is ok.
Bye,
Oleg
next prev parent reply other threads:[~2002-01-09 16:25 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
2002-01-09 16:25 ` Oleg Drokin [this message]
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=20020109192526.A1732@namesys.com \
--to=green@namesys.com \
--cc=adilger@turbolabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=mason@suse.com \
--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