From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from ms.lwn.net (ms.lwn.net [45.79.88.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id AF0FB217472; Tue, 12 Nov 2024 20:07:15 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=45.79.88.28 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1731442037; cv=none; b=mR3PJfFJxNRRQO5Vl25LdhXB9/H++/nAJ5bxpIPmH7JN9Cvnrdp2Td9FFUVHTcjh8iT4ZwQVmNNiHq7XjRU6WITPBaLOGyOO6cZptW5Xy4qgai0boMnbVy+obK2XDPfyPtYnajtJXIS5NIWyKNmxTBqtchQweAGVdY55Nz5liXo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1731442037; c=relaxed/simple; bh=VN4DPZ/Ubeh3yRvty7vLKSmzphCNXMsWhZKtu8onML8=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=NjvHHsOkyA3zbVolDvN+vTvfwzmLyD8IOusea/ZmaA3BN9yTlb+7DodklxpGrTvnCWswJwZdBZtERxYpwhB2DQ7r9HxH+0Jp3wdi3A3+lXWwL6aVzdGl9X2aRDjN0tM/tTrngNlpfFnG/5nR49vo5/EDZRhLgqqJUya6CYZFRvs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lwn.net; spf=pass smtp.mailfrom=lwn.net; dkim=pass (2048-bit key) header.d=lwn.net header.i=@lwn.net header.b=bM22XmXE; arc=none smtp.client-ip=45.79.88.28 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lwn.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lwn.net Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=lwn.net header.i=@lwn.net header.b="bM22XmXE" DKIM-Filter: OpenDKIM Filter v2.11.0 ms.lwn.net D3E66403E4 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lwn.net; s=20201203; t=1731442029; bh=u02gc8HT0igfeDobZAawC06098CdEuav8BmYMyCYA70=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=bM22XmXEfD+b/s4fGla3r+FP9+37fjjLLmC3Jv9po3J7gvVjV2VcKaOIVIGSzQ2fz scZDvVLPZ9+pE4lP1qedM12m9uK3WjDZks0AWQes/XqF2cV8LypoXvzO0n8nhM4auy ZxmVlqKsCgbPRqdTo3Q8ZX+BP/O+d/+qsq9Rw8hBf0t0NbX/lJvDX2auOpDWQ41YHp 2XWPA/j1TX4MGm+3j5tlMnQGYGS+KL6ZEuHTNx0xshP6G8o55oYgkVCxMH5OGD7HiF TxGdC62h16ShwQpSqtkC8BgnDqYjNQfHurT965EhCC/Cq6YK5X+3kM1DtpOkAK6Tj/ AmaCjMFJ7PFoA== Received: from localhost (unknown [IPv6:2601:280:5e00:625::1fe]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id D3E66403E4; Tue, 12 Nov 2024 20:07:08 +0000 (UTC) From: Jonathan Corbet To: Thorsten Leemhuis Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-next@vger.kernel.org, Mark Brown Subject: Re: [PATCH v3] docs: bug-bisect: add a note about bisecting -next In-Reply-To: References: Date: Tue, 12 Nov 2024 13:07:08 -0700 Message-ID: <87v7wsqkr7.fsf@trenco.lwn.net> Precedence: bulk X-Mailing-List: linux-next@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain Thorsten Leemhuis 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 > Signed-off-by: Mark Brown > Reviewed-by: Mark Brown > Signed-off-by: Thorsten Leemhuis > --- > 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