Linux Documentation
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Documentation <linux-doc@vger.kernel.org>,
	Linux bcachefs <linux-bcachefs@vger.kernel.org>,
	Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] Documentation: bcachefs: Add explicit title for idle work design doc
Date: Wed, 20 Aug 2025 10:11:52 +0700	[thread overview]
Message-ID: <aKU8-Bb1iIeYJTZQ@archie.me> (raw)
In-Reply-To: <yyqgq3brwrstiaqydzv4ua5syesrg4gh7w4uhtwg3flhuxa4ji@7xciwgaluwux>

[-- Attachment #1: Type: text/plain, Size: 686 bytes --]

On Tue, Aug 19, 2025 at 10:31:43PM -0400, Kent Overstreet wrote:
> On Wed, Aug 20, 2025 at 09:29:19AM +0700, Bagas Sanjaya wrote:
> > On Tue, Aug 19, 2025 at 09:08:22PM -0400, Kent Overstreet wrote:
> > > > -Idle/background work classes design doc:
> > > > +Idle/background work classes desiderata
> > > 
> > > .....
> > > what's going on with that spelling?
> > 
> > I'm just suggesting a better title, though. Should I keep it or revert back
> > to design doc?
> 
> Revert back to design doc, please.
> 
> (I genuinely had not seen that word before; usually prefer to keep
> things simple).

OK, thanks!

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-08-20  3:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-20  0:22 [PATCH] Documentation: bcachefs: Add explicit title for idle work design doc Bagas Sanjaya
2025-08-20  1:08 ` Kent Overstreet
2025-08-20  2:29   ` Bagas Sanjaya
2025-08-20  2:31     ` Kent Overstreet
2025-08-20  3:11       ` Bagas Sanjaya [this message]
2025-08-20  1:18 ` Randy Dunlap

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=aKU8-Bb1iIeYJTZQ@archie.me \
    --to=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@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