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

[PATCHv21 02/10] submodule-config: drop check against NULL

From
Stefan Beller <sbeller@google.com>
Date
Mar 1, 2016, 02:07 UTC
Message-ID
<1456798040-30129-3-git-send-email-sbeller@google.com>
In-Reply-To
<1456798040-30129-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.

Reviewed-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Stefan Beller <sbeller@google.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 submodule-config.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/submodule-config.c b/submodule-config.c
index a5cd2ee..9fa2269 100644
--- a/submodule-config.c
+++ b/submodule-config.c
@@ -267,7 +267,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 {
@@ -291,7 +291,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") &&
@@ -307,7 +307,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.8.0.rc0.1.g68b4e3f
Previous: Stefan BellerNext: Stefan Beller
Message 3 of 12 in “[PATCHv21 00/10] Expose submodule parallelism to the user”
  1. Stefan BellerMar 1, 2016
  2. 01/10 submodule-config: keep update strategy aroundStefan Beller, Mar 1, 2016
  3. 02/10 submodule-config: drop check against NULLStefan Beller, Mar 1, 2016
  4. 03/10 fetching submodules: respect `submodule.fetchJobs` config optionStefan Beller, Mar 1, 2016
  5. 04/10 submodule update: direct error message to stderrStefan Beller, Mar 1, 2016
  6. 05/10 run_processes_parallel: treat output of children as byte arrayStefan Beller, Mar 1, 2016
  7. 06/10 run_processes_parallel: rename parameters for the callbacksStefan Beller, Mar 1, 2016
  8. 07/10 git submodule update: have a dedicated helper for cloningStefan Beller, Mar 1, 2016
  9. 08/10 submodule helper: remove double 'fatal: ' prefixStefan Beller, Mar 1, 2016
  10. 09/10 submodule update: expose parallelism to the userStefan Beller, Mar 1, 2016
  11. 10/10 clone: allow an explicit argument for parallel submodule clonesStefan Beller, Mar 1, 2016
  12. Junio C HamanoMar 1, 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.