git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: David Aguilar <davvid@gmail.com>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: "Git Mailing List" <git@vger.kernel.org>,
	"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: Re: [PATCH RESEND] difftool: word spacing fix
Date: Mon, 20 Sep 2021 14:26:35 -0700	[thread overview]
Message-ID: <CAJDDKr4LfTC8h00NCLSu5J=oBTX3LWshrOXMQ7_iBi4RNie9sA@mail.gmail.com> (raw)
In-Reply-To: <20210920121627.905359-1-bagasdotme@gmail.com>

On Mon, Sep 20, 2021 at 5:19 AM Bagas Sanjaya <bagasdotme@gmail.com> wrote:
>
> Two grammar fixes related to word spacing:
>
>   - delete space in `non - zero`
>   - add space between diff formats/mode and option parentheses

The changes look like a good start, thanks.

Commit messages are written in an imperative tone, so this commit
message could be touched up.

Maybe?
---
difftool: fix word spacing in the usage strings

Remove spaces in `non - zero` and add a space between the diff
format/mode and option parentheses in difftool's usage strings.
---

But!.. and this is a big but... the po/ translations would be broken
by this change.

I'm unfamiliar with the policy about changes that affect translations,
but in general this seems like a situation where we can make things
easier for the translation team by not leaving behind further work.

My gut feeling is that this patch would be easier to accept if it also
updated the po/ translations to fix these typofixes.

Question for this list -- would that be a separate patch or not? To me
it seems like it'd all be one patch so that git is never in an
in-between state.

The following commands show a few places of interest that should also
be updated.

$ git grep 'combined diff formats('
$ git grep 'tool returns a non - zero'


>
> Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>
> Cc: David Aguilar <davvid@gmail.com>
> Cc: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
>  builtin/difftool.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/builtin/difftool.c b/builtin/difftool.c
> index 6a9242a803..ad9187761e 100644
> --- a/builtin/difftool.c
> +++ b/builtin/difftool.c
> @@ -410,9 +410,9 @@ static int run_dir_diff(const char *extcmd, int symlinks, const char *prefix,
>                 const char *src_path, *dst_path;
>
>                 if (starts_with(info.buf, "::"))
> -                       die(N_("combined diff formats('-c' and '--cc') are "
> +                       die(N_("combined diff formats ('-c' and '--cc') are "
>                                "not supported in\n"
> -                              "directory diff mode('-d' and '--dir-diff')."));
> +                              "directory diff mode ('-d' and '--dir-diff')."));
>
>                 if (parse_index_info(info.buf, &lmode, &rmode, &loid, &roid,
>                                      &status))
> @@ -713,7 +713,7 @@ int cmd_difftool(int argc, const char **argv, const char *prefix)
>                             "`--tool`")),
>                 OPT_BOOL(0, "trust-exit-code", &trust_exit_code,
>                          N_("make 'git-difftool' exit when an invoked diff "
> -                           "tool returns a non - zero exit code")),
> +                           "tool returns a non-zero exit code")),
>                 OPT_STRING('x', "extcmd", &extcmd, N_("command"),
>                            N_("specify a custom command for viewing diffs")),
>                 OPT_ARGUMENT("no-index", &no_index, N_("passed to `diff`")),
>
> base-commit: 4c719308ce59dc70e606f910f40801f2c6051b24
> --
> 2.25.1
>


--
David

  reply	other threads:[~2021-09-21  2:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-20 12:16 [PATCH RESEND] difftool: word spacing fix Bagas Sanjaya
2021-09-20 21:26 ` David Aguilar [this message]
2021-09-21  7:41   ` Bagas Sanjaya

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='CAJDDKr4LfTC8h00NCLSu5J=oBTX3LWshrOXMQ7_iBi4RNie9sA@mail.gmail.com' \
    --to=davvid@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=avarab@gmail.com \
    --cc=bagasdotme@gmail.com \
    --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.
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).