git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Chris P <christophe.poucet@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Stefan Xenos via GitGitGadget <gitgitgadget@gmail.com>,
	git@vger.kernel.org, Stefan Xenos <sxenos@google.com>
Subject: Re: [PATCH 07/10] evolve: implement the git change command
Date: Wed, 5 Oct 2022 14:30:18 +0200	[thread overview]
Message-ID: <CAN84kK=kTsy5stN7rR=EeLiTOq0si1UcmHfAE-UNvcofMSPKCg@mail.gmail.com> (raw)
In-Reply-To: <220926.8635ce4jox.gmgdl@evledraar.gmail.com>

On Mon, Sep 26, 2022 at 10:35 AM Ævar Arnfjörð Bjarmason
<avarab@gmail.com> wrote:
>
>
> On Fri, Sep 23 2022, Stefan Xenos via GitGitGadget wrote:
>
> > From: Stefan Xenos <sxenos@google.com>
>
> > +static const char * const builtin_change_usage[] = {
> > +     N_("git change update [--force] [--replace <treeish>...] [--origin <treesih>...] [--content <newtreeish>]"),
> > +     NULL
> > +};
> > +
> > +static const char * const builtin_update_usage[] = {
> > +     N_("git change update [--force] [--replace <treeish>...] [--origin <treesih>...] [--content <newtreeish>]"),
> > +     NULL
> > +};
>
> This (and the corresponding later *.txt version) should indent the
> overly long -h line, probably after "[--replace <treeish>...]".
>
> > +struct update_state {
> > +     int options;
>
> I think this should be an enum in your earlier 06/10. Makes things more
>
> > +             die(_("Failed to resolve '%s' as a valid revision."), committish);
>
> This and other error should start with a lower-case letter, see
> CodingGuidelines on errors.

Done.

>
> > [...]
> > +             die(_("Could not parse object '%s'."), committish);
>
> Ditto etc.
>
> > +     int i;
> > +     for (i = 0; i < commitsish_list->nr; i++) {
>
> A string_list uses a size_t for a nr, not int, so lets make that "size_t
> i".
>
> This both makes things more obvious, and helps some compilers spot
> unsigned v.s. signed issues.

Done.

>
>
> > +     int i;
>
> ditto size_t above...
>
> > +     for (i = 0; i < changes.nr; i++) {
>
> ...for this iteration...

Obsolete, moved to using for_each_string_list_item

>
> > +             struct string_list_item *it = &changes.items[i];
>
> ...but actually don't you just want for_each_string_list_item() instead?
>
> > +             if (it->util)
> > +                     fprintf(stdout, N_("Updated change %s\n"), name);
> > +             else
> > +                     fprintf(stdout, N_("Created change %s\n"), name);
>
> The use of N_() here is wrong, you should use _(), N_() just marks
> things for translation, but doesn't use it.
>

Done.

> We also tend to try to avoid adding \n in translations needlessly. And
> since you're printing to stdout this can be:
>
>
>         if (...)
>                 printf(_("Updated change %s"), name);
>         ...
>         putchar('\n')

Done

>
>
> > +     }
> > +
> > +     string_list_clear(&changes, 0);
> > +     change_table_clear(&chtable);
> > +     clear_metacommit_data(&metacommit);
> > +
> > +     return ret;
> > +}
> > +
> > +static int change_update(int argc, const char **argv, const char* prefix)
> > +{
> > +     int result;
> > +     int force = 0;
> > +     int newchange = 0;
> > +     struct strbuf err = STRBUF_INIT;
> > +     struct update_state state;
> > +     struct option options[] = {
> > +             { OPTION_CALLBACK, 'r', "replace", &state, N_("commit"),
> > +                     N_("marks the given commit as being obsolete"),
> > +                     0, update_option_parse_replace },
> > +             { OPTION_CALLBACK, 'o', "origin", &state, N_("commit"),
> > +                     N_("marks the given commit as being the origin of this commit"),
> > +                     0, update_option_parse_origin },
> > +             OPT_BOOL('F', "force", &force,
> > +                     N_("overwrite an existing change of the same name")),
> > +             OPT_STRING('c', "content", &state.content, N_("commit"),
> > +                              N_("identifies the new content commit for the change")),
> > +             OPT_STRING('g', "change", &state.change, N_("commit"),
> > +                              N_("name of the change to update")),
> > +             OPT_BOOL('n', "new", &newchange,
> > +                     N_("create a new change - do not append to any existing change")),
> > +             OPT_END()
> > +     };
> > +
> > +     init_update_state(&state);
> > +
> > +     argc = parse_options(argc, argv, prefix, options, builtin_update_usage, 0);
> > +
> > +     if (force) state.options |= UPDATE_OPTION_FORCE;
> > +     if (newchange) state.options |= UPDATE_OPTION_NOAPPEND;
>
> Just use OPT_SET_INT_F() and skip the indirection thorugh OPT_BOOL(),
> that macro itself is a thin wrapper for OPT_SET_INT_F().
>
> I.e. you can drop these "force" and "newchange" variables, andjust set
> your state.options directly.

Done.

>
> > +int cmd_change(int argc, const char **argv, const char *prefix)
> > +{
> > +     /* No options permitted before subcommand currently */
> > +     struct option options[] = {
> > +             OPT_END()
> > +     };
> > +     int result = 1;
> > +
> > +     argc = parse_options(argc, argv, prefix, options, builtin_change_usage,
> > +             PARSE_OPT_STOP_AT_NON_OPTION);
> > +
> > +     if (argc < 1)
> > +             usage_with_options(builtin_change_usage, options);
> > +     else if (!strcmp(argv[0], "update"))
> > +             result = change_update(argc, argv, prefix);
> > +     else {
> > +             error(_("Unknown subcommand: %s"), argv[0]);
> > +             usage_with_options(builtin_change_usage, options);
> > +     }
>
> This was presumably written before the recent OPT_SUBCOMMAND(), and
> should instead use that API.

Done, thanks!

  reply	other threads:[~2022-10-05 12:30 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 18:55 [PATCH 00/10] Add the Git Change command Christophe Poucet via GitGitGadget
2022-09-23 18:55 ` [PATCH 01/10] technical doc: add a design doc for the evolve command Stefan Xenos via GitGitGadget
2022-09-23 19:59   ` Jerry Zhang
2022-09-28 21:26   ` Junio C Hamano
2022-09-28 22:20   ` Junio C Hamano
2022-09-29  9:17     ` Phillip Wood
2022-09-29 19:57   ` Jonathan Tan
2022-09-23 18:55 ` [PATCH 02/10] sha1-array: implement oid_array_readonly_contains Chris Poucet via GitGitGadget
2022-09-26 13:08   ` Phillip Wood
2022-09-23 18:55 ` [PATCH 03/10] ref-filter: add the metas namespace to ref-filter Chris Poucet via GitGitGadget
2022-09-26 13:13   ` Phillip Wood
2022-10-04  9:50     ` Chris P
2022-09-23 18:55 ` [PATCH 04/10] evolve: add support for parsing metacommits Stefan Xenos via GitGitGadget
2022-09-26 13:27   ` Phillip Wood
2022-10-04 11:21     ` Chris P
2022-10-04 14:10       ` Phillip Wood
2022-09-23 18:55 ` [PATCH 05/10] evolve: add the change-table structure Stefan Xenos via GitGitGadget
2022-09-27 13:27   ` Phillip Wood
2022-09-27 13:50     ` Ævar Arnfjörð Bjarmason
2022-09-27 14:13       ` Phillip Wood
2022-09-27 15:28         ` Ævar Arnfjörð Bjarmason
2022-09-28 14:33           ` Phillip Wood
2022-09-28 15:14             ` Ævar Arnfjörð Bjarmason
2022-09-28 15:59             ` Junio C Hamano
2022-09-27 14:18     ` Phillip Wood
2022-10-04 14:48     ` Chris P
2022-09-23 18:55 ` [PATCH 06/10] evolve: add support for writing metacommits Stefan Xenos via GitGitGadget
2022-09-28 14:27   ` Phillip Wood
2022-10-05  9:40     ` Chris P
2022-10-05 11:09       ` Phillip Wood
2022-09-23 18:55 ` [PATCH 07/10] evolve: implement the git change command Stefan Xenos via GitGitGadget
2022-09-25  9:10   ` Phillip Wood
2022-09-26  8:23     ` Ævar Arnfjörð Bjarmason
2022-09-26  8:25   ` Ævar Arnfjörð Bjarmason
2022-10-05 12:30     ` Chris P [this message]
2022-09-23 18:55 ` [PATCH 08/10] evolve: add the git change list command Stefan Xenos via GitGitGadget
2022-09-23 18:55 ` [PATCH 09/10] evolve: add delete command Chris Poucet via GitGitGadget
2022-09-26  8:38   ` Ævar Arnfjörð Bjarmason
2022-09-26  9:10     ` Chris Poucet
2022-09-23 18:55 ` [PATCH 10/10] evolve: add documentation for `git change` Chris Poucet via GitGitGadget
2022-09-25  8:41   ` Phillip Wood
2022-09-25  8:39 ` [PATCH 00/10] Add the Git Change command Phillip Wood
2022-10-04  9:33   ` Chris P
2022-10-04 14:24 ` Phillip Wood
2022-10-04 15:19   ` Chris P
2022-10-04 15:55     ` Chris P
2022-10-04 16:00       ` Phillip Wood
2022-10-04 15:57     ` Phillip Wood
2022-10-05 14:59 ` [PATCH v2 00/10] RFC: Git Evolve / Change Christophe Poucet via GitGitGadget
2022-10-05 14:59   ` [PATCH v2 01/10] technical doc: add a design doc for the evolve command Stefan Xenos via GitGitGadget
2022-10-05 15:16     ` Chris Poucet
2022-10-06 20:53       ` Glen Choo
2022-10-10 19:35     ` Victoria Dye
2022-10-11  8:59       ` Phillip Wood
2022-10-11 16:59         ` Victoria Dye
2022-10-12 19:19           ` Phillip Wood
2022-10-05 14:59   ` [PATCH v2 02/10] sha1-array: implement oid_array_readonly_contains Chris Poucet via GitGitGadget
2022-10-05 14:59   ` [PATCH v2 03/10] ref-filter: add the metas namespace to ref-filter Chris Poucet via GitGitGadget
2022-10-05 14:59   ` [PATCH v2 04/10] evolve: add support for parsing metacommits Stefan Xenos via GitGitGadget
2022-10-05 14:59   ` [PATCH v2 05/10] evolve: add the change-table structure Stefan Xenos via GitGitGadget
2022-10-05 14:59   ` [PATCH v2 06/10] evolve: add support for writing metacommits Stefan Xenos via GitGitGadget
2022-10-05 14:59   ` [PATCH v2 07/10] evolve: implement the git change command Stefan Xenos via GitGitGadget
2022-10-05 14:59   ` [PATCH v2 08/10] evolve: add delete command Chris Poucet via GitGitGadget
2022-10-05 14:59   ` [PATCH v2 09/10] evolve: add documentation for `git change` Chris Poucet via GitGitGadget
2022-10-05 14:59   ` [PATCH v2 10/10] evolve: add tests for the git-change command Chris Poucet via GitGitGadget
2022-10-10  9:23   ` [PATCH v2 00/10] RFC: Git Evolve / Change Phillip Wood

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='CAN84kK=kTsy5stN7rR=EeLiTOq0si1UcmHfAE-UNvcofMSPKCg@mail.gmail.com' \
    --to=christophe.poucet@gmail.com \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=sxenos@google.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.
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).