linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Jens Axboe <axboe@kernel.dk>, Eric Biggers <ebiggers@kernel.org>
Cc: Bart Van Assche <bvanassche@acm.org>,
	linux-block@vger.kernel.org, linux-doc@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/8] docs: consolidate sysfs-block into Documentation/ABI/
Date: Mon, 10 Jan 2022 17:37:19 -0700	[thread overview]
Message-ID: <87k0f7hzuo.fsf@meer.lwn.net> (raw)
In-Reply-To: <fff11146-f759-2887-5c80-6449dbc16717@kernel.dk>

Jens Axboe <axboe@kernel.dk> writes:

> On 1/9/22 2:25 PM, Eric Biggers wrote:
>> I think it makes much more sense for subsystems to be responsible for
>> their own documentation; that's why patch 8 in this series adds the
>> block layer documentation to the block layer MAINTAINERS entry.  Do
>> you disagree with that?
>
> I agree, but then we often end up with merge conflicts between the doc
> tree and others. That's why it's usually punted there. As a maintainer,
> any conflicts is a pain in the butt to deal with, something the
> contributor doesn't necessarily see or understand.
>
> If there are no conflicts this time around, I can queue them up.

[Docs maintainer not copied on any of this, but you can't escape :)]

Maintaining docs is a bit of a challenge for the reason Jens mentions:
everybody puts their fingers into it, and the result is lots of merge
conflicts.  For that reason, I'd prefer that big changes go through the
docs tree.  Changes to directories like Documentation/ABI can be
especially prone to conflicts, FWIW.

I also tend to be a bit more attentive to things like the addition of
docs-build warnings than maintainers from other subsystems.

That said, the real goal is to get more and better documentation merged,
and it often does make the most sense for docs changes to go through
other trees.  Forcing the separation of documentation changes from the
code changes they reflect would be kind of silly at best, for example.
So if the block tree is the best path for these changes, then all I can
say is:

  Acked-by: Jonathan Corbet <corbet@lwn.net>

Thanks,

jon

  reply	other threads:[~2022-01-11  0:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-09  0:38 [PATCH v3 0/8] docs: consolidate sysfs-block into Documentation/ABI/ Eric Biggers
2021-12-09  0:38 ` [PATCH v3 1/8] docs: sysfs-block: move to stable directory Eric Biggers
2021-12-09  0:38 ` [PATCH v3 2/8] docs: sysfs-block: sort alphabetically Eric Biggers
2021-12-09  0:38 ` [PATCH v3 3/8] docs: sysfs-block: add contact for nomerges Eric Biggers
2021-12-09  0:38 ` [PATCH v3 4/8] docs: sysfs-block: fill in missing documentation from queue-sysfs.rst Eric Biggers
2021-12-09  0:38 ` [PATCH v3 5/8] docs: sysfs-block: document stable_writes Eric Biggers
2021-12-09  0:38 ` [PATCH v3 6/8] docs: sysfs-block: document virt_boundary_mask Eric Biggers
2021-12-09  0:38 ` [PATCH v3 7/8] docs: block: remove queue-sysfs.rst Eric Biggers
2021-12-09  0:38 ` [PATCH v3 8/8] MAINTAINERS: add entries for block layer documentation Eric Biggers
2021-12-21 15:41 ` [PATCH v3 0/8] docs: consolidate sysfs-block into Documentation/ABI/ Eric Biggers
2022-01-03 15:06   ` Eric Biggers
2022-01-06 21:41     ` Eric Biggers
2022-01-07 20:58       ` Bart Van Assche
2022-01-09 17:01         ` Jens Axboe
2022-01-09 21:25           ` Eric Biggers
2022-01-10  1:58             ` Jens Axboe
2022-01-11  0:37               ` Jonathan Corbet [this message]
2022-01-10  1:59 ` Jens Axboe

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=87k0f7hzuo.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=ebiggers@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).