From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 0E0063EBF1C; Sat, 24 Jan 2026 09:31:26 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769247087; cv=none; b=Ngk3x68aWU6fqD6jgN0XDA4drZhhvmcAmjO4PlGwsompHv1dXgAm88l9juNFUD0JJ5YQnZKqzcK8VFqhixJTkHLjXvJc962w+1YpGztG8ad+grnBYsxfFaDK/6rJM/6X/z1X7mNfCiN2CXFn4vv4yNUR/RjjDF3e8qTRe8nBgVc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769247087; c=relaxed/simple; bh=0boULBzOqolceekIbnAkeMqOMuPoOw+Ksf7bKBs+QHk=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=lWjotXcGQwYzMJRX/P36CpW9/LQncJdLt/ZnYWCwoiZzR7g0ykfXbHXYFIuzUB9GywCASSd+qosXY8+xSqsLtgQbvLRyDzAWvMh4PbmLb3V6khbyJKZAmYy42iimUgxbjqTTsco7poj35FUdFhOfKD05K0DxuZVVNfIigMu1Egk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=CkH0gr1M; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="CkH0gr1M" Received: by smtp.kernel.org (Postfix) with ESMTPSA id EE5CBC116D0; Sat, 24 Jan 2026 09:31:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1769247086; bh=0boULBzOqolceekIbnAkeMqOMuPoOw+Ksf7bKBs+QHk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=CkH0gr1MHVrTqs9ypGWulumOoRu7P2N+Sr5Z8jxpmfMztS2+hSFou0gPUSemUPxom AGE8c+qiH6jWfZRGd5W3/XG3zeqrQgB2HPoTtR0hvcDs7sMPSQucmF1WJEOolm0oyn 2TUIqWlSBSzzspeISAchUY8kfcjXpDAtWz4OS/WE= Date: Sat, 24 Jan 2026 10:31:23 +0100 From: Greg Kroah-Hartman To: Mauro Carvalho Chehab Cc: Dan Williams , corbet@lwn.net, ksummit@lists.linux.dev, linux-kernel@vger.kernel.org, tech-board-discuss@lists.linux.dev, Linus Torvalds , Miguel Ojeda , Kees Cook Subject: Re: [PATCH] Documentation: Project continuity Message-ID: <2026012441-jolliness-cringing-7e9f@gregkh> References: <20260124012256.1856709-1-dan.j.williams@intel.com> <20260124082939.40715e13@foz.lan> Precedence: bulk X-Mailing-List: ksummit@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260124082939.40715e13@foz.lan> On Sat, Jan 24, 2026 at 08:29:39AM +0100, Mauro Carvalho Chehab wrote: > On Fri, 23 Jan 2026 17:22:56 -0800 > Dan Williams wrote: > > > Document project continuity procedures. This is a plan for a plan for > > navigating events that affect the forward progress of the canonical Linux > > repository, torvalds/linux.git. It is a follow-up from Maintainer Summit > > [1]. > > The idea behind this document is interesting, but IMHO it is too > optimistic for a contingency plan ;-) > > Conceptually, contingency plans are written to overcome all foreseeable > bad consequences that might happen. So, it should include backups > for each possible bad scenario. That is not the goal here, we aren't going to enumerate all of the potential issues/plans for every possible scenario, that's just impossible and would take forever and likely result in something that is unworkable. This is here to say "these are the steps we will take to form a future plan if something goes wrong with our current one." thanks, greg k-h