Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Wang Shilong <wangsl.fnst@cn.fujitsu.com>
To: dsterba@suse.cz
Cc: "linux-btrfs@vger.kernel.org Btrfs" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs-progs: make send/receive compatible with older kernels
Date: Sat, 18 Jan 2014 13:30:08 +0800	[thread overview]
Message-ID: <52DA1160.50504@cn.fujitsu.com> (raw)
In-Reply-To: <20140114152756.GX6498@twin.jikos.cz>

Hi Dave,

On 01/14/2014 11:27 PM, David Sterba wrote:
> On Thu, Jan 09, 2014 at 02:52:27PM +0000, Chris Mason wrote:
>>>     You may need to upgrade the kernel to get new features offered by a
>>> new userspace, but I think we should absolutely not be changing
>>> userspace in a way that makes it incompatible with older kernels.
>> I'd really prefer that we maintain compatibility with the older kernels.
>> Heavy btrfs usage is going to want a newer kernel anyway, but this is an
>> important policy to keep in place for the future.
> I agree.
>
>> Especially since Wang went to the trouble of making the patch, I'd
>> rather take it.
> What do you think about adding #ifdef's around the code? That way we'll
> know that's for backwards compatibility only and up to what kernel
> version. It will be easier to remove it in the far future.
Sounds a good idea, would you describe it more specific so that
i can give a v2.^_^

Thanks,
Wang
>
>
> david
>


      reply	other threads:[~2014-01-18  5:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09 10:52 [PATCH] Btrfs-progs: make send/receive compatible with older kernels Wang Shilong
2014-01-09 11:49 ` Stefan Behrens
2014-01-09 11:56   ` Wang Shilong
2014-01-09 12:16   ` Hugo Mills
2014-01-09 14:52     ` Chris Mason
2014-01-14 15:27       ` David Sterba
2014-01-18  5:30         ` Wang Shilong [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=52DA1160.50504@cn.fujitsu.com \
    --to=wangsl.fnst@cn.fujitsu.com \
    --cc=dsterba@suse.cz \
    --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