diff options
| author |  Ævar Arnfjörð Bjarmason <avarab@gmail.com> | 2021-09-27 14:54:25 +0200 |
|---|---|---|
| committer |  Junio C Hamano <gitster@pobox.com> | 2021-09-27 14:47:59 -0700 |
| commit | 9865b6e6a4ca1e895fd473c827cf1822f3bd8249 (patch) | |
| tree | a042ff50d16f1a328592aa46a11311ab66585077 /checkout.c | |
| parent | submodule-config.h: remove unused SUBMODULE_INIT macro (diff) | |
| download | tgif-9865b6e6a4ca1e895fd473c827cf1822f3bd8249.tar.xz | |
*.[ch] *_INIT macros: use { 0 } for a "zero out" idiom
In C it isn't required to specify that all members of a struct are
zero'd out to 0, NULL or '\0', just providing a "{ 0 }" will
accomplish that.
Let's also change code that provided N zero'd fields to just
provide one, and change e.g. "{ NULL }" to "{ 0 }" for
consistency. I.e. even if the first member is a pointer let's use "0"
instead of "NULL". The point of using "0" consistently is to pick one,
and to not have the reader wonder why we're not using the same pattern
everywhere.
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'checkout.c')
| -rw-r--r-- | checkout.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/checkout.c b/checkout.c index 6586e30ca5..2e39dae684 100644 --- a/checkout.c +++ b/checkout.c @@ -14,7 +14,7 @@ struct tracking_name_data { struct object_id *default_dst_oid; }; -#define TRACKING_NAME_DATA_INIT { NULL, NULL, NULL, 0, NULL, NULL, NULL } +#define TRACKING_NAME_DATA_INIT { 0 } static int check_tracking_name(struct remote *remote, void *cb_data) { |