From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net [23.128.96.19]) (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 E37D62117 for ; Tue, 7 Nov 2023 03:25:15 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=none Received: from cloud.peff.net (cloud.peff.net [104.130.231.41]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 94881101 for ; Mon, 6 Nov 2023 19:25:14 -0800 (PST) Received: (qmail 27394 invoked by uid 109); 7 Nov 2023 03:25:14 -0000 Received: from Unknown (HELO peff.net) (10.0.1.2) by cloud.peff.net (qpsmtpd/0.94) with ESMTP; Tue, 07 Nov 2023 03:25:14 +0000 Authentication-Results: cloud.peff.net; auth=none Received: (qmail 9414 invoked by uid 111); 7 Nov 2023 03:25:15 -0000 Received: from coredump.intra.peff.net (HELO coredump.intra.peff.net) (10.0.0.2) by peff.net (qpsmtpd/0.94) with (TLS_AES_256_GCM_SHA384 encrypted) ESMTPS; Mon, 06 Nov 2023 22:25:15 -0500 Authentication-Results: peff.net; auth=none Date: Mon, 6 Nov 2023 22:25:11 -0500 From: Jeff King To: Junio C Hamano Cc: Joanna Wang , git@vger.kernel.org Subject: Re: Bug: magic-less pathspecs that start with ":" not processed as expected. Message-ID: <20231107032144.GA873619@coredump.intra.peff.net> References: <20231106173133.GC10414@coredump.intra.peff.net> Precedence: bulk X-Mailing-List: git@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: On Tue, Nov 07, 2023 at 08:29:34AM +0900, Junio C Hamano wrote: > Jeff King writes: > > > PS It took me a while to figure out where we document pathspec syntax. I > > wonder if a "gitpathspecs" manpage would make sense, like we have > > "gitrevisions". > > Yeah, I came to the same conclusion (should have saved time by > scanning the mailing list before I started writing my response) and > wondered where we wrote it down. The description you found in the > glossary, as far as I recall, is the authoritative one and looks > readable, but I agree it is not as discoverable as it should be. > > A simpler and more readable workaround than ":::file" is "./:file" > by the way ;-) Oh, indeed. That is much less horrible than ":(literal)". :) -Peff