From: kerylefondji7@gmail.com
To: gitster@pobox.com
Cc: git@vger.kernel.org, christiancouder@gmail.com,
siddharthasthana31@gmail.com,
kerylefondji <kerylefondji7@gmail.com>
Subject: [Outreachy][PATCH v2] builtin/var: refactor to use parse-options API
Date: Sat, 17 Oct 2026 12:25:09 +0100 [thread overview]
Message-ID: <20261017112518.4548-1-kerylefondji7@gmail.com> (raw)
In-Reply-To: <1a146af667a8bcd4>
From: kerylefondji <kerylefondji7@gmail.com>
Migrate option handling in 'git var' to the parse-options API.
This update also aligns variable resolution with current Git configuration
and attribute handling.
Signed-off-by: Keryle Blondeau Fondji Tamekong <keryle@DESKTOP-0SUCFI3>
---
builtin/var.c | 32 +++++++++++++++++++++++---------
1 file changed, 23 insertions(+), 9 deletions(-)
diff --git a/builtin/var.c b/builtin/var.c
index cc3a43cde2..b9234a55eb 100644
--- a/builtin/var.c
+++ b/builtin/var.c
@@ -3,11 +3,9 @@
*
* Copyright (C) Eric Biederman, 2005
*/
-
#define USE_THE_REPOSITORY_VARIABLE
#include "builtin.h"
-
#include "attr.h"
#include "config.h"
#include "editor.h"
@@ -18,8 +16,12 @@
#include "path.h"
#include "strbuf.h"
#include "run-command.h"
+#include "parse-options.h"
-static const char var_usage[] = "git var (-l | <variable>)";
+static const char * const var_usage[] = {
+ N_("git var (-l | <variable>)"),
+ NULL
+};
static char *committer(int ident_flag)
{
@@ -120,6 +122,7 @@ struct git_var {
char *(*read)(int);
int multivalued;
};
+
static struct git_var git_vars[] = {
{
.name = "GIT_COMMITTER_IDENT",
@@ -221,21 +224,32 @@ int cmd_var(int argc,
{
const struct git_var *git_var;
char *val;
+ int list = 0;
- show_usage_if_asked(argc, argv, var_usage);
- if (argc != 2)
- usage(var_usage);
+ struct option builtin_var_options[] = {
+ OPT_BOOL('l', "list", &list, N_("list builtin variables")),
+ OPT_END()
+ };
- if (strcmp(argv[1], "-l") == 0) {
+ argc = parse_options(argc, argv, prefix, builtin_var_options,
+ var_usage, 0);
+
+ if (list) {
+ if (argc > 0)
+ usage(var_usage[0]);
repo_config(the_repository, show_config, NULL);
list_vars();
return 0;
}
+
+ if (argc != 1)
+ usage(var_usage[0]);
+
repo_config(the_repository, git_default_config, NULL);
- git_var = get_git_var(argv[1]);
+ git_var = get_git_var(argv[0]);
if (!git_var)
- usage(var_usage);
+ usage(var_usage[0]);
val = git_var->read(IDENT_STRICT);
if (!val)
--
2.53.0
next prev parent reply other threads:[~2026-10-17 11:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1a146af667a8bcd4>
2026-10-17 0:54 ` [Outreachy][PATCH v2] builtin/var: refactor to use parse-options API Keryle
2026-10-17 11:25 ` kerylefondji7 [this message]
2026-10-17 11:45 ` Kristoffer Haugsbakk
2026-10-17 12:20 ` kerylefondji7
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261017112518.4548-1-kerylefondji7@gmail.com \
--to=kerylefondji7@gmail.com \
--cc=christiancouder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=siddharthasthana31@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox