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

[PATCHv10 2/7] submodule-config: drop check against NULL

From
Stefan Beller <sbeller@google.com>
Date
Feb 12, 2016, 02:03 UTC
Message-ID
<1455242592-19352-3-git-send-email-sbeller@google.com>
In-Reply-To
<1455242592-19352-1-git-send-email-sbeller@google.com>

Adhere to the common coding style of Git and not check explicitly for NULL throughout the file. There are still other occurrences in the code base but that is usually inside of conditions with side effects.

Signed-off-by: Stefan Beller <sbeller@google.com>
---
 submodule-config.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/submodule-config.c b/submodule-config.c
index 254067b..afd294b 100644
--- a/submodule-config.c
+++ b/submodule-config.c
@@ -295,7 +295,7 @@ static int parse_config(const char *var, const char *value, void *data)
 	if (!strcmp(item.buf, "path")) {
 		if (!value)
 			ret = config_error_nonbool(var);
-		else if (!me->overwrite && submodule->path != NULL)
+		else if (!me->overwrite && submodule->path)
 			warn_multiple_config(me->commit_sha1, submodule->name,
 					"path");
 		else {
@@ -319,7 +319,7 @@ static int parse_config(const char *var, const char *value, void *data)
 	} else if (!strcmp(item.buf, "ignore")) {
 		if (!value)
 			ret = config_error_nonbool(var);
-		else if (!me->overwrite && submodule->ignore != NULL)
+		else if (!me->overwrite && submodule->ignore)
 			warn_multiple_config(me->commit_sha1, submodule->name,
 					"ignore");
 		else if (strcmp(value, "untracked") &&
@@ -335,7 +335,7 @@ static int parse_config(const char *var, const char *value, void *data)
 	} else if (!strcmp(item.buf, "url")) {
 		if (!value) {
 			ret = config_error_nonbool(var);
-		} else if (!me->overwrite && submodule->url != NULL) {
+		} else if (!me->overwrite && submodule->url) {
 			warn_multiple_config(me->commit_sha1, submodule->name,
 					"url");
 		} else {
-- 
2.7.1.292.g18a4ced.dirty
Previous: Stefan BellerNext: Stefan Beller
Message 3 of 9 in “[PATCHv10 0/7] Expose submodule parallelism to the user”
  1. Stefan BellerFeb 12, 2016
  2. 1/7 submodule-config: keep update strategy aroundStefan Beller, Feb 12, 2016
  3. 2/7 submodule-config: drop check against NULLStefan Beller, Feb 12, 2016
  4. 3/7 fetching submodules: respect `submodule.fetchJobs` config optionStefan Beller, Feb 12, 2016
  5. 4/7 submodule update: direct error message to stderrStefan Beller, Feb 12, 2016
  6. 5/7 git submodule update: have a dedicated helper for cloningStefan Beller, Feb 12, 2016
  7. Stefan BellerFeb 12, 2016
  8. 6/7 submodule update: expose parallelism to the userStefan Beller, Feb 12, 2016
  9. 7/7 clone: allow an explicit argument for parallel submodule clonesStefan Beller, Feb 12, 2016

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.