All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Rubén Justo" <rjusto@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH] branch: error code with --edit-description
Date: Tue, 25 Oct 2022 16:43:48 -0700	[thread overview]
Message-ID: <xmqqv8o7mpu3.fsf@gitster.g> (raw)
In-Reply-To: <b0f96b35-4e69-a889-bcdf-e0b40b89384f@gmail.com> ("Rubén Justo"'s message of "Wed, 26 Oct 2022 00:57:18 +0200")

Rubén Justo <rjusto@gmail.com> writes:

> Since c2d17ba3db0d (branch --edit-description: protect against mistyped
> branch name, 2012-02-05) we return -1 on error editing the branch
> description.
>
> Let's change to 1, which follows the established convention and it is
> better for portability reasons.

Nicely explained.  As ret is initialized to 1 to assume failure (and
we set it to 0 when we are happy), the change to stop assigning the
return value from error() is a very sensible implementation, too.

Will queue.  Thanks.

>
> Signed-off-by: Rubén Justo <rjusto@gmail.com>
> ---
>  builtin/branch.c  | 2 +-
>  t/t3200-branch.sh | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/builtin/branch.c b/builtin/branch.c
> index c964ac7bb4..15be0c03ef 100644
> --- a/builtin/branch.c
> +++ b/builtin/branch.c
> @@ -809,7 +809,7 @@ int cmd_branch(int argc, const char **argv, const char *prefix)
>  
>  		strbuf_addf(&branch_ref, "refs/heads/%s", branch_name);
>  		if (!ref_exists(branch_ref.buf))
> -			ret = error((!argc || !strcmp(head, branch_name))
> +			error((!argc || !strcmp(head, branch_name))
>  			      ? _("No commit on branch '%s' yet.")
>  			      : _("No branch named '%s'."),
>  			      branch_name);
> diff --git a/t/t3200-branch.sh b/t/t3200-branch.sh
> index 38c57de71b..7f605f865b 100755
> --- a/t/t3200-branch.sh
> +++ b/t/t3200-branch.sh
> @@ -1394,7 +1394,7 @@ test_expect_success 'branch --delete --force removes dangling branch' '
>  
>  test_expect_success 'use --edit-description' '
>  	EDITOR=: git branch --edit-description &&
> -	test_must_fail git config branch.main.description &&
> +	test_expect_code 1 git config branch.main.description &&
>  
>  	write_script editor <<-\EOF &&
>  		echo "New contents" >"$1"

      reply	other threads:[~2022-10-25 23:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25 22:57 [PATCH] branch: error code with --edit-description Rubén Justo
2022-10-25 23:43 ` Junio C Hamano [this message]

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=xmqqv8o7mpu3.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=rjusto@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.