> This is obviously not the behavior the user wanted, so let's fix this by > specifically setting the submodule as inactive in this case when we're > cloning the repository. This is a > problem because we will have skipped cloning or checking out the > submodule, and as a result, other commands, such as git reset or git > checkout, will fail if they are invoked with -recurse-submodules (or > when submodule.recurse is true). > When the user recursively clones a repository with submodules and one or > more of those submodules is marked with the submodule.update=none > configuration, the submodule will end up being active. Setting, so we don't want to set such a configuration option then. Update, where we explicitly indicate that we override the configuration Submodule helper is also invoked during a user-invoked git submodule Note that we only do this when the -require-init option is passed, That will make us properly ignore the submodule Specifically setting the submodule as inactive in this case when we'reĬloning the repository. This is obviously not the behavior the user wanted, so let's fix this by Submodule, and as a result, other commands, such as git reset or gitĬheckout, will fail if they are invoked with -recurse-submodules (or Problem because we will have skipped cloning or checking out the More of those submodules is marked with the submodule.update=noneĬonfiguration, the submodule will end up being active. When the user recursively clones a repository with submodules and one or X-Mailing-List: mark submodules with update=none as inactiveīrian m.
Subject: submodule: mark submodules with update=none as inactive U3IkoFSn9PR9lRGqRAjpFDwe5+DNBndlGpz39sBl+ikTgxXJBvd Tn5v3ToFoQQcvouNcKm5V9nCMbSBhfOEScgwWLNj/eB7lfMxJGJ8sTl0Ev5/OUM1TV +4Xc84EH+aJVtHcHIUQZ1p9Xu6F2ITs0LweJFdXOOEWwnb4r9rZD2tiQNMXvvuDDFz UG/1WgJFolcc1k4562DOmQUC1cpbTrVScYqlNnbV1F69V17zfrp/rKreqFRUca3EQl Uv4lJrDJO0MppA7gxqEymrMIBYlMOg4phXnoBa/6gt7VbalvsYGBrwEwwkU0YYlx+/ XSukW/8Lk5EErprEwmdjgGjMdPaClkKSu0Wr3dnhD/rOdUTg70/RXN3OGM22CJvoIb In-Reply-To:References:Content-Type:Content-Disposition ī=i8wu8phlk8vXnfkgoFK//hYCnY31xViyKH599E7I3hcAYJHv1GHhsR5W2Jc3f9wblĪoMEtsvLKGF2jCdEocQKIpl+GlNFrtzZ7mJL81DHvao5fs6lUQNIZEo3GtN+XceP27 Subject:Date:To:CC:Resent-Date:Resent-From:Resent-To:Resent-Cc:
H=From:To:Cc:Subject:Date:In-Reply-To:References:From:Reply-To: (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits))īy (Postfix) with ESMTPSA idĭKIM-Signature: v=1 a=rsa-sha256 c=relaxed/simple d= īh=NGDEhOKSQLzYo3tuRgCKXFJzWZ8ssAaGsltDw1KMLl8= " rhost-flags-OK-OK-OK-OK)īy with ESMTP id S229521AbhFSVrN (ORCPT Received: from ( )īy (Postfix) with ESMTP id 47F5C601FE Received: from ( )īy (Postfix) with ESMTP id 74914C2B9F4
INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_GITĪutolearn=ham autolearn_force=no version=3.4.0 X-Spam-Status: No, score=-18.8 required=3.0 tests=BAYES_00,DKIM_SIGNED,ĭKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER, X-Spam-Checker-Version: SpamAssassin 3.4.0 () onĪ
0 kommentar(er)
