public inbox for tools@linux.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Brigham Campbell <me@brighamcampbell.com>
Cc: tools@kernel.org
Subject: Re: [PATCH] Fix typo in maintainer docs
Date: Wed, 11 Mar 2026 10:39:09 -0400	[thread overview]
Message-ID: <20260311-invaluable-attentive-gopher-dd0a55@lemur> (raw)
In-Reply-To: <20260311074014.289088-1-me@brighamcampbell.com>

On Wed, Mar 11, 2026 at 01:40:14AM -0600, Brigham Campbell wrote:
> Fix a minor typo in the documentation for `b4 review`.

It's not actually a typo. ;) Welcome to the Canadian spelling where we
arbitrarily spell some things the US way and others the UK way, and many of
them are correct both ways! Like enroll and enrol, which are both accepted in
Canadian spelling. *sigh*

However, since the command is "b4 enroll" and not "b4 enrol" I will take the
patch.

> Signed-off-by: Brigham Campbell <me@brighamcampbell.com>
> ---
> 
> Unrelated, but thanks for your work on b4, Konstantin. It's been a
> wonderful help to me so far. I expect the new review functionalities to
> be very useful for reviewing many patches from kernel mentees.

Thank you! That's my hope as well.

Cheers,
-K

>  Enrolling a repository
>  ~~~~~~~~~~~~~~~~~~~~~~
> -Before you can track series, you need to enrol the repository::
> +Before you can track series, you need to enroll the repository::
>  
>      b4 review enroll [path] [-i identifier]
>  
> 
> base-commit: cba5b5a9fd6078646a58531643e7365480504d77
> -- 
> 2.52.0
> 

-- 
KR

  reply	other threads:[~2026-03-11 14:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11  7:40 [PATCH] Fix typo in maintainer docs Brigham Campbell
2026-03-11 14:39 ` Konstantin Ryabitsev [this message]
2026-03-11 15:27   ` Vlastimil Babka
2026-03-11 15:29     ` Konstantin Ryabitsev
2026-03-11 19:23   ` Brigham Campbell
2026-03-11 15:19 ` Konstantin Ryabitsev

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=20260311-invaluable-attentive-gopher-dd0a55@lemur \
    --to=konstantin@linuxfoundation.org \
    --cc=me@brighamcampbell.com \
    --cc=tools@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