Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2A7FCC7EE2D for ; Fri, 3 Mar 2023 18:49:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231715AbjCCStP (ORCPT ); Fri, 3 Mar 2023 13:49:15 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58400 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231131AbjCCStL (ORCPT ); Fri, 3 Mar 2023 13:49:11 -0500 Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 00DA05585 for ; Fri, 3 Mar 2023 10:48:51 -0800 (PST) Received: from cwcc.thunk.org (pool-173-48-120-46.bstnma.fios.verizon.net [173.48.120.46]) (authenticated bits=0) (User authenticated as tytso@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 323Imihg032215 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 3 Mar 2023 13:48:45 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mit.edu; s=outgoing; t=1677869325; bh=bDj2qFEVaDFepzsMbUQBiP7to8SePon9vUB3eBFG99U=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=hyKDcdkrojaRaHfCgAmfrMRaL5IMF7i1NSDn7810f1ELBgeSTQ1pVkeDp7aoyWGws EluYbuXjauFsGVpSGRBouyNJ4cqjSGvXSW8yTKhzB8P5XM8d/BgbrrspWM6zsa1GPq tS0Ksp+vMPeZIgaTP4suxdACeHr1of8HkJBbWvJHLVK79I12zJLI6iMhR+bw0Q06+n Y270414MqqiAhGPUiEkgaz8Z9Sji3Z/r2szNtBDW8Vrf9z3lZWBFu27DzQskSIBpxi IHBSaOEwk2Cdc02fipT3DMxbVbOYVlYw20Tt4RbiiT0EbS9OAi8nj/P5d4nxPUDndN Dc6nM+vYKDTWQ== Received: by cwcc.thunk.org (Postfix, from userid 15806) id 0B18A15C33A7; Fri, 3 Mar 2023 13:48:44 -0500 (EST) Date: Fri, 3 Mar 2023 13:48:44 -0500 From: "Theodore Ts'o" To: Nick Terrell Cc: Linus Torvalds , Linux Kernel Mailing List , Nick Terrell Subject: Re: [GIT PULL] zstd changes for v6.3-rc1 Message-ID: References: <4BA6A759-F69C-406E-9D29-EDCC9B48F798@meta.com> <2B90FACE-74EB-47C8-91FD-62E3F77B95EC@meta.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2B90FACE-74EB-47C8-91FD-62E3F77B95EC@meta.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 03, 2023 at 06:03:50PM +0000, Nick Terrell wrote: > > What do you prefer I do with my current tree? I guess I can either: > - Leave the merges in and keep a stable tree > - Fix up my tree and clean up the merges, but break the stable tree Do you have any downstream trees that depend on your tree? If you don't anyone who might be using your tree as a base for forther work (linux-next doesn't count, since it rewinds every working day). In general, for most "leaf" trees, rewinding your branches is not a big deal. There are some people who worship at the altar of "stable git branches which never be rewound, forever and ever, Amen". But that is really a religious belief, and it's one that I don't subscribe to. Sure, if someone is depending on your git tree then rewinding the branch can cause them problems. But not all subsystem trees are used by others as a basis for further work! There are benefits to rewinding / rebasing patches; sometimes I'll do rewind the ext4 dev branch to add a "Tested-By", or to drop a patch which I had merged, but then later on I discovered that it causes regressions. In that case, I'll drop the patch using git rebase -i since it can make life easier who are doing git bisects. Cheers, - Ted