Git development
 help / color / mirror / Atom feed
From: Kenneth Lorber <keni@his.com>
To: git@vger.kernel.org
Cc: Kenneth Lorber <keni@his.com>
Subject: [PATCH v2 0/1] config: surface editor failure in exit code
Date: Wed, 19 Aug 2026 11:09:19 -0400	[thread overview]
Message-ID: <20260819150922.2984850-3-keni@his.com> (raw)
In-Reply-To: <20260819150922.2984850-1-keni@his.com>

(Apologies to anyone who gets this twice.)

Simplified the tests and changed the test names from "--edit" to "-e"
since that's what the test is actually running.  Did not change the
tests to use "--edit" as nothing else is checking "-e".


1:  d54d260aa0 ! 1:  05d02b80dc config: surface editor failure in exit code
     @@ t/t1300-config.sh: test_expect_success 'command line overrides environment config' '
      	test_cmp expect actual
      '
      
    -+test_expect_success 'git config --edit successful exit' '
    ++test_expect_success 'git config -e successful exit' '
     +	test_when_finished "rm -rf repo" &&
     +	git init repo &&
    -+	GIT_EDITOR=true &&
    -+	export GIT_EDITOR &&
    -+	git -C repo config -e &&
    -+	unset GIT_EDITOR
    ++	test_env GIT_EDITOR=true git -C repo config -e
     +'
     +
    -+test_expect_success 'git config --edit failure exit' '
    ++test_expect_success 'git config -e failure exit' '
     +	test_when_finished "rm -rf repo" &&
     +	git init repo &&
    -+	GIT_EDITOR=false &&
    -+	export GIT_EDITOR &&
    -+	test_must_fail git -C repo config -e &&
    -+	unset GIT_EDITOR
    ++	test_env GIT_EDITOR=false test_must_fail git -C repo config -e
     +'
     +
      test_expect_success 'git config --edit works' '
--
2.43.0



  parent reply	other threads:[~2026-08-19 15:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17 21:19 [RFC PATCH 0/1] config: surface editor failure in exit code Kenneth Lorber
2026-08-17 21:19 ` [RFC PATCH 1/1] " Kenneth Lorber
2026-08-18  8:42   ` Karthik Nayak
2026-08-19 11:17     ` Kenneth Lorber
2026-08-19 20:11     ` Junio C Hamano
2026-08-17 22:39 ` [RFC PATCH 0/1] " Junio C Hamano
2026-08-18  8:26   ` Karthik Nayak
2026-08-18 14:31     ` Junio C Hamano
2026-08-18 22:12       ` brian m. carlson
2026-08-19 15:09 ` [PATCH v2 " Kenneth Lorber
2026-08-19 15:09   ` [PATCH v2 1/1] " Kenneth Lorber
2026-08-19 15:09   ` Kenneth Lorber [this message]
2026-08-19 15:09   ` Kenneth Lorber
2026-08-19 17:58   ` [PATCH v2 0/1] " Junio C Hamano
2026-08-19 18:58     ` Kenneth Lorber
2026-08-19 19:24       ` 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=20260819150922.2984850-3-keni@his.com \
    --to=keni@his.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox