From: "bolide2005@163.com" <bolide2005@163.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Bug or just a mistake : --shallow-exclude parameter behavior anomalies in Git 2.45.2: "no commits selected" and "ambiguous deepen-not" errors
Date: Thu, 20 Feb 2025 16:26:34 +0800 [thread overview]
Message-ID: <2025022016263355354612@163.com> (raw)
When using git clone with --shallow-exclude parameter (specifying branch name or existing commit SHA-1), two different errors occur:
Case 1: git clone --shallow-exclude=master <repo-url>
Error: fatal: no commits selected for shallow requests
Case 2: git clone --shallow-exclude=ef5974fc470ad7a08f9b58dcd78724e9329910db <repo-url>
Error: git upload-pack: ambiguous deepen-not: deepen-not ef5974fc470ad7a08f9b58dcd78724e9329910db
Git Version: 2.45.2 (Confirmed on Centos 7)
bolide2005@163.com
next reply other threads:[~2025-02-20 8:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 8:26 bolide2005 [this message]
2025-02-24 15:27 ` Bug or just a mistake : --shallow-exclude parameter behavior anomalies in Git 2.45.2: "no commits selected" and "ambiguous deepen-not" errors Elijah Newren
2025-09-16 14:50 ` --shallow-exclude=ref -> "ambiguous deepen-not" error Philipp Hahn
2025-09-16 17:03 ` D. Ben Knoble
2025-09-16 17:57 ` Philipp Hahn
2025-09-16 20:34 ` Ben Knoble
2025-09-17 2:54 ` Elijah Newren
2025-10-21 12:08 ` Erik Cervin Edin
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=2025022016263355354612@163.com \
--to=bolide2005@163.com \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.