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

[PATCHv20 02/12] submodule-config: drop check against NULL

From
Stefan Beller <sbeller@google.com>
Date
Feb 29, 2016, 19:14 UTC
Message-ID
<1456773250-5510-3-git-send-email-sbeller@google.com>
In-Reply-To
<1456773250-5510-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.7.0.rc0.37.gb7b9e8e
Previous: Stefan BellerNext: Stefan Beller
Message 3 of 16 in “[PATCHv20 00/12] Expose submodule parallelism to the user”
  1. Stefan BellerFeb 29, 2016
  2. 01/12 submodule-config: keep update strategy aroundStefan Beller, Feb 29, 2016
  3. 02/12 submodule-config: drop check against NULLStefan Beller, Feb 29, 2016
  4. 03/12 fetching submodules: respect `submodule.fetchJobs` config optionStefan Beller, Feb 29, 2016
  5. 04/12 submodule update: direct error message to stderrStefan Beller, Feb 29, 2016
  6. 05/12 run_processes_parallel: treat output of children as byte arrayStefan Beller, Feb 29, 2016
  7. 06/12 run-command: expose default_{start_failure, task_finished}Stefan Beller, Feb 29, 2016
  8. 07/12 run_processes_parallel: rename parameters for the callbacksStefan Beller, Feb 29, 2016
  9. 08/12 run_processes_parallel: correctly terminate callbacks with an LFStefan Beller, Feb 29, 2016
  10. 09/12 git submodule update: have a dedicated helper for cloningStefan Beller, Feb 29, 2016
  11. 10/12 submodule helper: remove double 'fatal: ' prefixStefan Beller, Feb 29, 2016
  12. 11/12 submodule update: expose parallelism to the userStefan Beller, Feb 29, 2016
  13. 12/12 clone: allow an explicit argument for parallel submodule clonesStefan Beller, Feb 29, 2016
  14. Jonathan NiederFeb 29, 2016
  15. Stefan BellerFeb 29, 2016
  16. Junio C HamanoFeb 29, 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.