public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Theodore Tso <tytso@mit.edu>,
	linux-kernel@vger.kernel.org, phillip@lougher.demon.co.uk,
	linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Documentation/Changes: add required versions for new filesystems
Date: Wed, 28 Jan 2009 19:45:10 -0800	[thread overview]
Message-ID: <49812646.306@oracle.com> (raw)
In-Reply-To: <20090128211347.GG8990@mit.edu>

Theodore Tso wrote:
> On Wed, Jan 28, 2009 at 11:01:57AM -0500, Bill Nottingham wrote:
>> Bill Nottingham (notting@redhat.com) said: 
>>> btrfs requires version 0.18 of its tools, and squashfs requires
>>> 4.0.
>> This time, with a typo fix.
> 
> While you're at it, could you also update e2fsprogs to require 1.41.4.
> It's required for ext4, and even for ext3, if the text is going to
> say, "if you're going to report any bugs, please update to the
> versions of these programs".  So the line for e2fsprogs should read:
> 
>  o  e2fsprogs              1.41.4                    # e2fsck -V
> 
> I could push this as a separate patch, but then there could be patch
> conflicts, so it might be nice if you could update e2fsprogs at the
> same time.

I've done that and can add it to my Docs patches queue for Linus.

Thanks,
-- 
~Randy

      reply	other threads:[~2009-01-29  3:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-28 16:00 [PATCH] Documentation/Changes: add required versions for new filesystems Bill Nottingham
2009-01-28 16:01 ` Bill Nottingham
2009-01-28 21:13   ` Theodore Tso
2009-01-29  3:45     ` Randy Dunlap [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=49812646.306@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phillip@lougher.demon.co.uk \
    --cc=tytso@mit.edu \
    /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