All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: ritvikfoss@gmail.com
Cc: linux-doc@vger.kernel.org, skhan@linuxfoundation.org,
	linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH] documentation/filesystems: fix spelling mistakes
Date: Mon, 10 Feb 2025 10:47:11 -0700	[thread overview]
Message-ID: <87frkl1ylc.fsf@trenco.lwn.net> (raw)
In-Reply-To: <20250210043937.30952-1-ritvikfoss@gmail.com>

ritvikfoss@gmail.com writes:

> From: Ritvik Gupta <ritvikfoss@gmail.com>
>
> Corrected the following spelling mistakes,
> based on the suggestions by codespell:
>
> 1. Optionaly   -> Optionally
> 2. prefereable -> preferable
> 3. peformance  -> performance
> 4. ontext      -> context
> 5. failuer     -> failure
> 6. poiners     -> pointers
> 7. realtively  -> relatively
> 8. uptream     -> upstream
>
> Thanks for your time!
> Regards Ritvik
>
> Signed-off-by: Ritvik Gupta <ritvikfoss@gmail.com>
> ---
>  Documentation/filesystems/9p.rst                              | 2 +-
>  Documentation/filesystems/bcachefs/SubmittingPatches.rst      | 4 ++--
>  Documentation/filesystems/coda.rst                            | 2 +-
>  Documentation/filesystems/debugfs.rst                         | 2 +-
>  Documentation/filesystems/netfs_library.rst                   | 2 +-
>  Documentation/filesystems/xfs/xfs-delayed-logging-design.rst  | 2 +-
>  .../filesystems/xfs/xfs-maintainer-entry-profile.rst          | 2 +-
>  7 files changed, 8 insertions(+), 8 deletions(-)

I've applied this, but ... for future reference ...

- As Randy noted, the "thanks" message doesn't belong in the changelog;
  I took it out.

- It's not really necessary to list every word you've fixed; "fix some
  misspellings" is sufficient.  I left those in though :)

- This patch did not apply to docs-next - the bcachefs file you change
  only showed up in the mainline yesterday.  I pulled docs-next forward
  to -rc2 to avoid making you redo it, but it's better not to make
  maintainers do that in general.  The proper approach, which would have
  been needed for a more involved change, would have been to send that
  fix to the bcachefs maintainer instead to go through his tree.

Thanks,

jon

  parent reply	other threads:[~2025-02-10 17:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-10  4:39 [PATCH] documentation/filesystems: fix spelling mistakes ritvikfoss
2025-02-10  5:49 ` Randy Dunlap
2025-02-11  1:05   ` Ritvik Gupta
2025-02-10 17:47 ` Jonathan Corbet [this message]
2025-02-11  4:33   ` Ritvik Gupta

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=87frkl1ylc.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=ritvikfoss@gmail.com \
    --cc=skhan@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.