From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: george espinoza via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, George Espinoza <gespinoz2019@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
george espinoza <gespinoz2019@gmail.com>
Subject: Re: [PATCH 1/1] [Outreachy] merge-ours: include parse-options
Date: Tue, 29 Oct 2019 13:56:01 +0100 (CET) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1910291355070.46@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <8c088194f604eac3a6b00c48a7fddfdf807571fc.1572306149.git.gitgitgadget@gmail.com>
Hi george,
On Mon, 28 Oct 2019, george espinoza via GitGitGadget wrote:
> From: george espinoza <gespinoz2019@gmail.com>
>
> Teach this command which currently handles its own argv to use
> parse-options instead because parse-options helps make sure we handle
> user input like -h in a standardized way across the project.
> Also deleted the NO_PARSEOPT flag from git.c to coincide with
> the conversion of the structure in this command since merge-ours
> now uses parse-options and needed to update git.c accordingly.
The commit message and the patch look good to me!
Thanks,
Johannes
>
> Signed-off-by: george espinoza <gespinoz2019@gmail.com>
> ---
> builtin/merge-ours.c | 14 ++++++++++----
> git.c | 2 +-
> 2 files changed, 11 insertions(+), 5 deletions(-)
>
> diff --git a/builtin/merge-ours.c b/builtin/merge-ours.c
> index 4594507420..fb3674a384 100644
> --- a/builtin/merge-ours.c
> +++ b/builtin/merge-ours.c
> @@ -11,14 +11,20 @@
> #include "git-compat-util.h"
> #include "builtin.h"
> #include "diff.h"
> +#include "parse-options.h"
>
> -static const char builtin_merge_ours_usage[] =
> - "git merge-ours <base>... -- HEAD <remote>...";
> +static const char * const merge_ours_usage[] = {
> + N_("git merge-ours [<base>...] -- <head> <merge-head>..."),
> + NULL,
> +};
>
> int cmd_merge_ours(int argc, const char **argv, const char *prefix)
> {
> - if (argc == 2 && !strcmp(argv[1], "-h"))
> - usage(builtin_merge_ours_usage);
> + struct option options[] = {
> + OPT_END()
> + };
> +
> + argc = parse_options(argc, argv, prefix, options, merge_ours_usage, 0);
>
> /*
> * The contents of the current index becomes the tree we
> diff --git a/git.c b/git.c
> index ce6ab0ece2..6aee0e9477 100644
> --- a/git.c
> +++ b/git.c
> @@ -527,7 +527,7 @@ static struct cmd_struct commands[] = {
> { "merge-base", cmd_merge_base, RUN_SETUP },
> { "merge-file", cmd_merge_file, RUN_SETUP_GENTLY },
> { "merge-index", cmd_merge_index, RUN_SETUP | NO_PARSEOPT },
> - { "merge-ours", cmd_merge_ours, RUN_SETUP | NO_PARSEOPT },
> + { "merge-ours", cmd_merge_ours, RUN_SETUP },
> { "merge-recursive", cmd_merge_recursive, RUN_SETUP | NEED_WORK_TREE | NO_PARSEOPT },
> { "merge-recursive-ours", cmd_merge_recursive, RUN_SETUP | NEED_WORK_TREE | NO_PARSEOPT },
> { "merge-recursive-theirs", cmd_merge_recursive, RUN_SETUP | NEED_WORK_TREE | NO_PARSEOPT },
> --
> gitgitgadget
>
next prev parent reply other threads:[~2019-10-29 12:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 23:42 [PATCH 0/1] [Outreachy] merge-ours: include a parse-option George Espinoza via GitGitGadget
2019-10-28 23:42 ` [PATCH 1/1] [Outreachy] merge-ours: include parse-options george espinoza via GitGitGadget
2019-10-29 12:56 ` Johannes Schindelin [this message]
2019-10-29 20:42 ` Emily Shaffer
2019-10-30 9:43 ` George Espinoza
2019-10-30 2:05 ` Junio C Hamano
2019-10-30 9:53 ` George Espinoza
2019-10-30 21:58 ` Johannes Schindelin
2019-11-02 4:14 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.6.1910291355070.46@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=gespinoz2019@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.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;
as well as URLs for NNTP newsgroup(s).