patches and low-level development discussion
 help / color / mirror / code / Atom feed
From: Alyssa Ross <hi@alyssa.is>
To: Valentin Gagarin <valentin@gagarin.work>
Cc: devel@spectrum-os.org
Subject: Re: [PATCH] Documentation: move b4 guide to the back
Date: Fri, 24 Jul 2026 14:49:15 +0200	[thread overview]
Message-ID: <874ihotuwk.fsf@alyssa.is> (raw)
In-Reply-To: <20260722005817.1274433-1-valentin@gagarin.work>

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

Valentin Gagarin <valentin@gagarin.work> writes:

> It's not needed for getting started with contributions.
>
> Signed-off-by: Valentin Gagarin <valentin@gagarin.work>
> ---
>  Documentation/doc/contributing/b4.adoc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/doc/contributing/b4.adoc b/Documentation/doc/contributing/b4.adoc
> index 3734c3a..cc12018 100644
> --- a/Documentation/doc/contributing/b4.adoc
> +++ b/Documentation/doc/contributing/b4.adoc
> @@ -1,5 +1,5 @@
>  = Installing and Configuring b4
> -:page-nav_order: 1
> +:page-nav_order: 3
>  
>  // SPDX-FileCopyrightText: 2022 Alyssa Ross <hi@alyssa.is>
>  // SPDX-License-Identifier: GFDL-1.3-no-invariants-or-later OR CC-BY-SA-4.0
> -- 
> 2.54.0

Yep, makes sense as we currently have things.  New people do seem to
broadly like using b4 for everything including submission though, so in
the long term it might make more sense to introduce it earlier and port
all the contributing documentation to the b4 ways.

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

  reply	other threads:[~2026-07-24 12:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22  0:58 [PATCH] Documentation: move b4 guide to the back Valentin Gagarin
2026-07-24 12:49 ` Alyssa Ross [this message]
2026-07-24 12:58 ` Alyssa Ross

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=874ihotuwk.fsf@alyssa.is \
    --to=hi@alyssa.is \
    --cc=devel@spectrum-os.org \
    --cc=valentin@gagarin.work \
    /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.
Code repositories for project(s) associated with this public inbox

	https://spectrum-os.org/git/doc
	https://spectrum-os.org/git/mktuntap
	https://spectrum-os.org/git/spectrum
	https://spectrum-os.org/git/ucspi-vsock

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).