From: Christoph Hellwig <hch@lst.de>
To: Philipp Reisner <philipp.reisner@linbit.com>
Cc: Christoph Hellwig <hch@lst.de>,
Lars Ellenberg <lars.ellenberg@linbit.com>,
Jens Axboe <axboe@kernel.dk>,
drbd-dev@lists.linbit.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: state of drbd in mainline
Date: Tue, 29 Mar 2022 09:32:54 +0200 [thread overview]
Message-ID: <20220329073254.GA20691@lst.de> (raw)
In-Reply-To: <CADGDV=UgjZAbmAN-2bO1nyDvA=XCC9Lf2dxWHZ0BwxF12nnztQ@mail.gmail.com>
On Tue, Mar 29, 2022 at 09:22:26AM +0200, Philipp Reisner wrote:
> Hi Christoph,
>
> what do you expect for the DRBD changes? Usually, they fall into the
> category: yes, obviously. When you are changing the block layer in this
> way, then that is necessary for the in-tree DRBD code.
>
> Regarding users: Yes, there are users of the in-tree DRBD code. Very big
> corporations. And, yes, we see pressure building up that we get our act
> together and re-sync the in-tree DRBD with the out-of tree DRBD.
The complete lack of bug reports and maintainer interaction usually
suggests low to no use and heavy bitrot. If that is not the case
here that's fine, just asking..
next prev parent reply other threads:[~2022-03-29 7:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 7:06 state of drbd in mainline Christoph Hellwig
2022-03-29 7:24 ` Philipp Reisner
[not found] ` <CADGDV=UgjZAbmAN-2bO1nyDvA=XCC9Lf2dxWHZ0BwxF12nnztQ@mail.gmail.com>
2022-03-29 7:32 ` Christoph Hellwig [this message]
2022-03-29 7:50 ` Philipp Reisner
2022-03-29 12:29 ` Jens Axboe
2022-03-29 15:44 ` Philipp Reisner
2022-03-29 15:52 ` Jens Axboe
2022-03-30 15:23 ` Philipp Reisner
2022-03-30 18:06 ` Mike Snitzer
2022-03-30 18:24 ` Jens Axboe
2022-03-30 19:31 ` [Drbd-dev] " Kiselev, Oleg
2022-03-30 20:21 ` Jens Axboe
2022-03-29 20:01 ` Wolfgang Walter
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=20220329073254.GA20691@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=drbd-dev@lists.linbit.com \
--cc=lars.ellenberg@linbit.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=philipp.reisner@linbit.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