Re: [PATCH] Fix off by one error in prep_exclude.

From: Junio C Hamano <gitster@pobox.com>
Date: Jan 28, 2008, 02:52 UTC
Message-ID: <7vodb6wtix.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <20080128003404.GA18276@lintop>

Shawn Bohrer <shawn.bohrer@gmail.com> writes:

Show 8 quoted lines

> Nope the problem Johannes Sixt was having was that he mistakenly ran
>
> git clean -n /*foo
>
> Now that isn't what he meant to do, but I figured it might be possible
> that someone has their whole filesystem in a git repository, or maybe
> is using some sort of chroot on their repository.  Your malformed
> paths guess is probably much more likely to occur.

That is not a user error from the syntax point of view (although it might be from the semantics point of view). I think the caller of the excluded() function (that is probably somewhere in builtin-clean.c -- I did not check) is responsible for not supplying such a path to the called function.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.