Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Anand Jain <anand.jain@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: doc: btrfs device assembly and verification
Date: Mon, 3 Jun 2024 22:50:43 +0200	[thread overview]
Message-ID: <20240603205043.GE12376@twin.jikos.cz> (raw)
In-Reply-To: <792a9315d9f68d4222aad02a3f245a0f4b63c96b.1716446880.git.anand.jain@oracle.com>

On Thu, May 23, 2024 at 03:10:32PM +0530, Anand Jain wrote:
> Create a document on how devices are assembled and their verification
> steps.

Thanks. This seems to be a developer documentation, for which you should
put it to dev/ and link it from the respective section in index.rst.

There's some information about the device assembly from user perspective
too, that should go to the user documentation.

      reply	other threads:[~2024-06-03 20:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-23  9:40 [PATCH] btrfs-progs: doc: btrfs device assembly and verification Anand Jain
2024-06-03 20:50 ` David Sterba [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=20240603205043.GE12376@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=anand.jain@oracle.com \
    --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