From: Andreas Ericsson <ae@op5.se>
To: David Bryson <david@statichacks.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Use "git_config_string" to simplify "remote.c" code in "handle_config"
Date: Fri, 03 Oct 2008 07:28:42 +0200 [thread overview]
Message-ID: <48E5AD8A.4070301@op5.se> (raw)
In-Reply-To: <20081003033937.GA11594@eratosthenes.cryptobackpack.org>
David Bryson wrote:
> Signed-off-by: David Bryson <david@statichacks.org>
>
> I tried to keep with the naming/coding conventions that I found in
> remote.c. Feedback welcome.
>
> ---
> remote.c | 19 ++++++++++---------
> 1 files changed, 10 insertions(+), 9 deletions(-)
>
> diff --git a/remote.c b/remote.c
> index 3f3c789..893a739 100644
> --- a/remote.c
> +++ b/remote.c
> @@ -305,6 +305,7 @@ static int handle_config(const char *key, const char *value, void *cb)
> {
> const char *name;
> const char *subkey;
> + const char *v;
Not very mnemonic. I'm sure you can think up a better name, even if it's
a long one. Git is notoriously sparse when it comes to comments. We rely
instead on self-explanatory code.
> struct remote *remote;
> struct branch *branch;
> if (!prefixcmp(key, "branch.")) {
> @@ -314,15 +315,15 @@ static int handle_config(const char *key, const char *value, void *cb)
> return 0;
> branch = make_branch(name, subkey - name);
> if (!strcmp(subkey, ".remote")) {
> - if (!value)
> - return config_error_nonbool(key);
> - branch->remote_name = xstrdup(value);
> + if (git_config_string(&v, key, value) )
> + return -1;
> + branch->remote_name = v;
> if (branch == current_branch)
> default_remote_name = branch->remote_name;
> } else if (!strcmp(subkey, ".merge")) {
> - if (!value)
> - return config_error_nonbool(key);
> - add_merge(branch, xstrdup(value));
> + if (git_config_string(&v, key, value ))
> + return -1;
> + add_merge(branch, v);
> }
> return 0;
> }
> @@ -334,9 +335,9 @@ static int handle_config(const char *key, const char *value, void *cb)
> return 0;
> rewrite = make_rewrite(name, subkey - name);
> if (!strcmp(subkey, ".insteadof")) {
> - if (!value)
> - return config_error_nonbool(key);
> - add_instead_of(rewrite, xstrdup(value));
> + if (git_config_string(&v, key, value ))
> + return -1;
> + add_instead_of(rewrite, v);
> }
> }
> if (prefixcmp(key, "remote."))
Other than that, the patch looks good.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2008-10-03 5:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 3:39 [PATCH] Use "git_config_string" to simplify "remote.c" code in "handle_config" David Bryson
2008-10-03 5:28 ` Andreas Ericsson [this message]
2008-10-03 20:06 ` David Bryson
2008-10-04 22:46 ` Alex Riesen
2008-10-06 19:49 ` David Bryson
2008-10-06 14:13 ` Johannes Schindelin
2008-10-06 19:53 ` David Bryson
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=48E5AD8A.4070301@op5.se \
--to=ae@op5.se \
--cc=david@statichacks.org \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).