From: Jonathan Corbet <corbet@lwn.net>
To: Thorsten Leemhuis <linux@leemhuis.info>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH v3] docs: bug-bisect: add a note about bisecting -next
Date: Tue, 12 Nov 2024 13:07:08 -0700 [thread overview]
Message-ID: <87v7wsqkr7.fsf@trenco.lwn.net> (raw)
In-Reply-To: <ec19d5fc503ff7db3d4c4ff9e97fff24cc78f72a.1730808651.git.linux@leemhuis.info>
Thorsten Leemhuis <linux@leemhuis.info> writes:
> Explicitly mention how to bisect -next, as nothing in the kernel tree
> currently explains that bisects between -next versions won't work well
> and it's better to bisect between mainline and -next.
>
> Co-developed-by: Mark Brown <broonie@kernel.org>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> Reviewed-by: Mark Brown <broonie@kernel.org>
> Signed-off-by: Thorsten Leemhuis <linux@leemhuis.info>
> ---
> v3
> - add a optional 'that' for readability/understandability
>
> v2:
> - slightly change patch descption
> - make the text more how-toish to better match the rest of the document
>
> v1: https://lore.kernel.org/all/20241022-doc-bisect-next-v1-1-196c0a60d554@kernel.org/
> - initial release
> ---
> Documentation/admin-guide/bug-bisect.rst | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
Applied, thanks.
jon
prev parent reply other threads:[~2024-11-12 20:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 12:11 [PATCH v3] docs: bug-bisect: add a note about bisecting -next Thorsten Leemhuis
2024-11-06 1:04 ` Bagas Sanjaya
2024-11-06 5:26 ` Thorsten Leemhuis
2024-11-06 10:15 ` Bagas Sanjaya
2024-11-06 10:35 ` Thorsten Leemhuis
2024-11-06 10:41 ` Bagas Sanjaya
2024-11-06 10:43 ` Bagas Sanjaya
2024-11-12 20:07 ` Jonathan Corbet [this message]
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=87v7wsqkr7.fsf@trenco.lwn.net \
--to=corbet@lwn.net \
--cc=broonie@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@leemhuis.info \
/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