From: Jay Soffian <jaysoffian@gmail.com>
To: git@vger.kernel.org
Cc: Jay Soffian <jaysoffian@gmail.com>, Jeff King <peff@peff.net>,
Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 11/23] builtin-remote: rename variable and eliminate redundant function call
Date: Tue, 24 Feb 2009 04:50:59 -0500 [thread overview]
Message-ID: <c2de944b2fc5315c2d0f88cb16ad8b17033329a7.1235467368.git.jaysoffian@gmail.com> (raw)
In-Reply-To: <cover.1235467368.git.jaysoffian@gmail.com>
The variable name "remote" is used as both a "char *" and as a "struct
remote *"; this is confusing, so rename the former to remote_name.
There is no need to call "sort_string_list(&branch_list)" as branch_list
is populated via string_list_insert(), which maintains its order.
Signed-off-by: Jay Soffian <jaysoffian@gmail.com>
---
builtin-remote.c | 13 ++++++-------
1 files changed, 6 insertions(+), 7 deletions(-)
diff --git a/builtin-remote.c b/builtin-remote.c
index 608c0f3..48d668e 100644
--- a/builtin-remote.c
+++ b/builtin-remote.c
@@ -144,7 +144,7 @@ static int add(int argc, const char **argv)
}
struct branch_info {
- char *remote;
+ char *remote_name;
struct string_list merge;
};
@@ -183,9 +183,9 @@ static int config_read_branches(const char *key, const char *value, void *cb)
item->util = xcalloc(sizeof(struct branch_info), 1);
info = item->util;
if (type == REMOTE) {
- if (info->remote)
+ if (info->remote_name)
warning("more than one branch.%s", key);
- info->remote = xstrdup(value);
+ info->remote_name = xstrdup(value);
} else {
char *space = strchr(value, ' ');
value = abbrev_branch(value);
@@ -207,7 +207,6 @@ static void read_branches(void)
if (branch_list.nr)
return;
git_config(config_read_branches, NULL);
- sort_string_list(&branch_list);
}
struct ref_states {
@@ -489,7 +488,7 @@ static int mv(int argc, const char **argv)
for (i = 0; i < branch_list.nr; i++) {
struct string_list_item *item = branch_list.items + i;
struct branch_info *info = item->util;
- if (info->remote && !strcmp(info->remote, rename.old)) {
+ if (info->remote_name && !strcmp(info->remote_name, rename.old)) {
strbuf_reset(&buf);
strbuf_addf(&buf, "branch.%s.remote", item->string);
if (git_config_set(buf.buf, rename.new)) {
@@ -599,7 +598,7 @@ static int rm(int argc, const char **argv)
for (i = 0; i < branch_list.nr; i++) {
struct string_list_item *item = branch_list.items + i;
struct branch_info *info = item->util;
- if (info->remote && !strcmp(info->remote, remote->name)) {
+ if (info->remote_name && !strcmp(info->remote_name, remote->name)) {
const char *keys[] = { "remote", "merge", NULL }, **k;
for (k = keys; *k; k++) {
strbuf_reset(&buf);
@@ -742,7 +741,7 @@ static int show(int argc, const char **argv)
struct branch_info *info = branch->util;
int j;
- if (!info->merge.nr || strcmp(*argv, info->remote))
+ if (!info->merge.nr || strcmp(*argv, info->remote_name))
continue;
printf(" Remote branch%s merged with 'git pull' "
"while on branch %s\n ",
--
1.6.2.rc1.291.g83eb
next prev parent reply other threads:[~2009-02-24 9:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1235467368.git.jaysoffian@gmail.com>
2009-02-24 9:50 ` [PATCH 01/23] builtin-clone: move locate_head() to remote.c so it can be re-used Jay Soffian
2009-02-24 9:50 ` [PATCH 02/23] builtin-remote: move duplicated cleanup code its own function Jay Soffian
2009-02-24 9:50 ` [PATCH 03/23] builtin-remote: teach show to display remote HEAD Jay Soffian
2009-02-24 9:50 ` [PATCH 04/23] builtin-remote: add set-head subcommand Jay Soffian
2009-02-24 9:50 ` [PATCH 05/23] builtin-remote: better handling of multiple remote HEADs Jay Soffian
2009-02-24 9:50 ` [PATCH 06/23] remote.c: make match_refs() copy src ref before assigning to peer_ref Jay Soffian
2009-02-24 9:50 ` [PATCH 07/23] remote.c: don't short-circuit match_refs() when error in match_explicit_refs() Jay Soffian
2009-02-24 9:50 ` [PATCH 08/23] refactor duplicated get_local_heads() to remote.c Jay Soffian
2009-02-24 9:50 ` [PATCH 09/23] refactor duplicated ref_newer() " Jay Soffian
2009-02-24 9:50 ` [PATCH 10/23] string-list: new for_each_string_list() function Jay Soffian
2009-02-24 9:50 ` Jay Soffian [this message]
2009-02-24 9:51 ` [PATCH 12/23] builtin-remote: name remote_refs consistently Jay Soffian
2009-02-24 9:51 ` [PATCH 13/23] builtin-remote: remove unused code in get_ref_states Jay Soffian
2009-02-24 9:51 ` [PATCH 14/23] builtin-remote: fix two inconsistencies in the output of "show <remote>" Jay Soffian
2009-02-24 9:51 ` [PATCH 15/23] builtin-remote: make get_remote_ref_states() always populate states.tracked Jay Soffian
2009-02-24 9:51 ` [PATCH 16/23] builtin-remote: refactor get_remote_ref_states() Jay Soffian
2009-02-24 9:51 ` [PATCH 17/23] builtin-remote: new show output style Jay Soffian
2009-02-24 9:51 ` [PATCH 18/23] builtin-remote: new show output style for push refspecs Jay Soffian
2009-02-24 9:51 ` [PATCH 19/23] test scripts: refactor start_httpd helper Jay Soffian
2009-02-24 9:51 ` [PATCH 20/23] add basic http clone/fetch tests Jay Soffian
2009-02-24 9:51 ` [PATCH 21/23] refactor find_refs_by_name to accept const list Jay Soffian
2009-02-24 9:51 ` [PATCH 22/23] remote: refactor guess_remote_head Jay Soffian
2009-02-24 9:51 ` [PATCH 23/23] remote: use exact HEAD lookup if it is available Jay Soffian
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=c2de944b2fc5315c2d0f88cb16ad8b17033329a7.1235467368.git.jaysoffian@gmail.com \
--to=jaysoffian@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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).