From: Ben Peart <peartben@gmail.com>
To: Kevin Willford <kewillf@microsoft.com>, git@vger.kernel.org
Cc: gitster@pobox.com, peff@peff.net
Subject: Re: [PATCH 2/3] merge-recursive: remove return value from get_files_dirs
Date: Mon, 28 Aug 2017 18:45:29 -0400 [thread overview]
Message-ID: <8f1a7139-6f5b-eb47-ecb6-ded1d550b06a@gmail.com> (raw)
In-Reply-To: <20170828202829.3056-3-kewillf@microsoft.com>
On 8/28/2017 4:28 PM, Kevin Willford wrote:
> The return value of the get_files_dirs call is never being used.
> Looking at the history of the file and it was originally only
> being used for debug output statements. Also when
> read_tree_recursive return value is non zero it is changed to
> zero. This leads me to believe that it doesn't matter if
> read_tree_recursive gets an error.
>
> Since the debug output has been removed and the caller isn't
> checking the return value there is no reason to keep calulating
> and returning a value.
>
Did a quick search and you're right, nothing is using the return value.
No reason to spend time calculating it. Looks good.
> Signed-off-by: Kevin Willford <kewillf@microsoft.com>
> ---
> merge-recursive.c | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/merge-recursive.c b/merge-recursive.c
> index 033d7cd406..d47f40ea81 100644
> --- a/merge-recursive.c
> +++ b/merge-recursive.c
> @@ -328,15 +328,11 @@ static int save_files_dirs(const unsigned char *sha1,
> return (S_ISDIR(mode) ? READ_TREE_RECURSIVE : 0);
> }
>
> -static int get_files_dirs(struct merge_options *o, struct tree *tree)
> +static void get_files_dirs(struct merge_options *o, struct tree *tree)
> {
> - int n;
> struct pathspec match_all;
> memset(&match_all, 0, sizeof(match_all));
> - if (read_tree_recursive(tree, "", 0, 0, &match_all, save_files_dirs, o))
> - return 0;
> - n = o->current_file_set.nr + o->current_directory_set.nr;
> - return n;
> + read_tree_recursive(tree, "", 0, 0, &match_all, save_files_dirs, o);
> }
>
> /*
>
next prev parent reply other threads:[~2017-08-28 22:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 20:28 [PATCH 0/3] merge-recursive: replace string_list with hashmap Kevin Willford
2017-08-28 20:28 ` [PATCH 1/3] merge-recursive: fix memory leak Kevin Willford
2017-08-28 22:42 ` Ben Peart
2017-08-29 8:12 ` Jeff King
2017-08-28 20:28 ` [PATCH 2/3] merge-recursive: remove return value from get_files_dirs Kevin Willford
2017-08-28 22:45 ` Ben Peart [this message]
2017-08-29 8:19 ` Jeff King
2017-08-29 8:17 ` Jeff King
2017-08-29 15:58 ` Kevin Willford
2017-08-29 16:50 ` Jeff King
2017-08-31 18:12 ` Stefan Beller
2017-08-28 20:28 ` [PATCH 3/3] merge-recursive: change current file dir string_lists to hashmap Kevin Willford
2017-08-28 23:06 ` Ben Peart
2017-08-29 8:41 ` Jeff King
2017-09-06 3:35 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8f1a7139-6f5b-eb47-ecb6-ded1d550b06a@gmail.com \
--to=peartben@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kewillf@microsoft.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).