From: Dave Chinner <david@fromorbit.com>
To: Gabriel Niebler <gniebler@suse.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH 0/4] README: Fix setup, btrfs and distro info
Date: Fri, 4 Mar 2022 10:47:59 +1100 [thread overview]
Message-ID: <20220303234759.GI3927073@dread.disaster.area> (raw)
In-Reply-To: <20220303132804.4151-1-gniebler@suse.com>
On Thu, Mar 03, 2022 at 02:28:00PM +0100, Gabriel Niebler wrote:
> The README had some incorrect environment setup information in the quick start
> section and some outdated info related to btrfs testing.
>
> This patchset fixes that, while also adding some more distro specfic setup info.
>
> Gabriel Niebler (4):
> README: Fix environment setup quick start
> README: Adjust and add btrfs testing information
> README: Add command to install required packages on SUSE
> README: Fix indentation to be consistent
This document is in the process of a major update:
https://lore.kernel.org/fstests/20220228202849.183568-1-aalbersh@redhat.com/T/#m257b55c7ee6a2fb3de17df5ea2c575e2541e01f6
It would be best to check whether these issues still need fixing
after the above patch is applied and then rebase the changes on top
of that to be consistent with the new structure and layout.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2022-03-03 23:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 13:28 [PATCH 0/4] README: Fix setup, btrfs and distro info Gabriel Niebler
2022-03-03 13:28 ` [PATCH 1/4] README: Fix environment setup quick start Gabriel Niebler
2022-03-03 13:28 ` [PATCH 2/4] README: Adjust and add btrfs testing information Gabriel Niebler
2022-03-03 13:28 ` [PATCH 3/4] README: Add command to install required packages on SUSE Gabriel Niebler
2022-03-03 13:28 ` [PATCH 4/4] README: Fix indentation to be consistent Gabriel Niebler
2022-03-03 23:47 ` Dave Chinner [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=20220303234759.GI3927073@dread.disaster.area \
--to=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=gniebler@suse.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