git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] remote.c: correct the check for a leading '/' in a remote name

From
Brandon Casey <casey@nrlssc.navy.mil>
Date
Oct 14, 2008, 20:30 UTC
Message-ID
<J-KL1Cgc2b78Lced5uBNDhP0MHdg91do73K_0waicFQYbDZHjYkocw@cipher.nrlssc.navy.mil>

This test is supposed to disallow remote entries in the config file of the form:

   [remote "/foobar"]
      ...
The leading slash in '/foobar' is not acceptable.

Instead it was incorrectly testing that the subkey had no leading '/', which had no effect since the subkey pointer was made to point at a '.' in the preceding lines.

Signed-off-by: Brandon Casey <casey@nrlssc.navy.mil>
---

I stumbled across this code which looks like a mistake. This patch seems like the correct fix.

-brandon
 remote.c |    9 +++++----
 1 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/remote.c b/remote.c
index d5efadd..8a04066 100644
--- a/remote.c
+++ b/remote.c
@@ -341,13 +341,14 @@ static int handle_config(const char *key, const char *value, void *cb)
 	if (prefixcmp(key,  "remote."))
 		return 0;
 	name = key + 7;
+	if (*name == '/') {
+		warning("Config remote shorthand cannot begin with '/': %s",
+			name);
+		return 0;
+	}
 	subkey = strrchr(name, '.');
 	if (!subkey)
 		return error("Config with no key for remote %s", name);
-	if (*subkey == '/') {
-		warning("Config remote shorthand cannot begin with '/': %s", name);
-		return 0;
-	}
 	remote = make_remote(name, subkey - name);
 	if (!strcmp(subkey, ".mirror"))
 		remote->mirror = git_config_bool(key, value);
-- 
1.6.0.2.468.gd5b83
Next: Daniel Barkalow
Message 1 of 2 in “remote.c: correct the check for a leading '/' in a remote name”
  1. remote.c: correct the check for a leading '/' in a remote nameBrandon Casey, Oct 14, 2008
  2. Daniel BarkalowOct 14, 2008

Read the whole thread, see it on lore, or plain text.

$ 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.