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

[PATCHv19 02/11] submodule-config: drop check against NULL

From
Stefan Beller <sbeller@google.com>
Date
Feb 25, 2016, 23:48 UTC
Message-ID
<1456444119-6934-3-git-send-email-sbeller@google.com>
In-Reply-To
<1456444119-6934-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>
---
 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.36.g75877e4.dirty
Previous: Stefan BellerNext: Stefan Beller
Message 37 of 59 in “[PATCHv17 00/11] Expose submodule parallelism to the user”
  1. Stefan BellerFeb 25, 2016
  2. 01/11 submodule-config: keep update strategy aroundStefan Beller, Feb 25, 2016
  3. Junio C HamanoFeb 25, 2016
  4. Stefan BellerFeb 25, 2016
  5. 02/11 submodule-config: drop check against NULLStefan Beller, Feb 25, 2016
  6. 03/11 fetching submodules: respect `submodule.fetchJobs` config optionStefan Beller, Feb 25, 2016
  7. 04/11 submodule update: direct error message to stderrStefan Beller, Feb 25, 2016
  8. 05/11 run_processes_parallel: treat output of children as byte arrayStefan Beller, Feb 25, 2016
  9. Junio C HamanoFeb 25, 2016
  10. Stefan BellerFeb 25, 2016
  11. 06/11 run-command: expose default_{start_failure, task_finished}Stefan Beller, Feb 25, 2016
  12. 07/11 run_processes_parallel: rename parameters for the callbacksStefan Beller, Feb 25, 2016
  13. 08/11 run_processes_parallel: correctly terminate callbacks with an LFStefan Beller, Feb 25, 2016
  14. 09/11 git submodule update: have a dedicated helper for cloningStefan Beller, Feb 25, 2016
  15. 10/11 submodule update: expose parallelism to the userStefan Beller, Feb 25, 2016
  16. 11/11 clone: allow an explicit argument for parallel submodule clonesStefan Beller, Feb 25, 2016
  17. Junio C HamanoFeb 25, 2016
  18. 00/11 ExposeStefan Beller, Feb 25, 2016
  19. 01/11 submodule-config: keep update strategy aroundStefan Beller, Feb 25, 2016
  20. 02/11 submodule-config: drop check against NULLStefan Beller, Feb 25, 2016
  21. 03/11 fetching submodules: respect `submodule.fetchJobs` config optionStefan Beller, Feb 25, 2016
  22. 04/11 submodule update: direct error message to stderrStefan Beller, Feb 25, 2016
  23. 05/11 run_processes_parallel: treat output of children as byte arrayStefan Beller, Feb 25, 2016
  24. 06/11 run-command: expose default_{start_failure, task_finished}Stefan Beller, Feb 25, 2016
  25. 07/11 run_processes_parallel: rename parameters for the callbacksStefan Beller, Feb 25, 2016
  26. 08/11 run_processes_parallel: correctly terminate callbacks with an LFStefan Beller, Feb 25, 2016
  27. 09/11 git submodule update: have a dedicated helper for cloningStefan Beller, Feb 25, 2016
  28. 10/11 submodule update: expose parallelism to the userStefan Beller, Feb 25, 2016
  29. 11/11 clone: allow an explicit argument for parallel submodule clonesStefan Beller, Feb 25, 2016
  30. Stefan BellerFeb 25, 2016
  31. Jonathan NiederFeb 25, 2016
  32. Stefan BellerFeb 25, 2016
  33. Jonathan NiederFeb 25, 2016
  34. Junio C HamanoFeb 25, 2016
  35. 00/11 Expose submodule parallelism to the userStefan Beller, Feb 25, 2016
  36. 01/11 submodule-config: keep update strategy aroundStefan Beller, Feb 25, 2016
  37. 02/11 submodule-config: drop check against NULLStefan Beller, Feb 25, 2016
  38. 03/11 fetching submodules: respect `submodule.fetchJobs` config optionStefan Beller, Feb 25, 2016
  39. 04/11 submodule update: direct error message to stderrStefan Beller, Feb 25, 2016
  40. 05/11 run_processes_parallel: treat output of children as byte arrayStefan Beller, Feb 25, 2016
  41. 06/11 run-command: expose default_{start_failure, task_finished}Stefan Beller, Feb 25, 2016
  42. 07/11 run_processes_parallel: rename parameters for the callbacksStefan Beller, Feb 25, 2016
  43. 08/11 run_processes_parallel: correctly terminate callbacks with an LFStefan Beller, Feb 25, 2016
  44. 09/11 git submodule update: have a dedicated helper for cloningStefan Beller, Feb 25, 2016
  45. Duy NguyenFeb 27, 2016
  46. Stefan BellerFeb 29, 2016
  47. 10/11 submodule update: expose parallelism to the userStefan Beller, Feb 25, 2016
  48. 11/11 clone: allow an explicit argument for parallel submodule clonesStefan Beller, Feb 25, 2016
  49. Jonathan NiederFeb 25, 2016
  50. Johannes SixtFeb 29, 2016
  51. Stefan BellerFeb 29, 2016
  52. Junio C HamanoFeb 29, 2016
  53. Stefan BellerFeb 29, 2016
  54. Junio C HamanoFeb 29, 2016
  55. Stefan BellerFeb 29, 2016
  56. Johannes SixtFeb 29, 2016
  57. Junio C HamanoFeb 29, 2016
  58. Stefan BellerFeb 29, 2016
  59. Jonathan NiederFeb 25, 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.