Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Re: [PATCH v2 4/4] add: introduce '--resolved' option
Date: Wed, 29 Jul 2026 15:19:53 -0700	[thread overview]
Message-ID: <xmqqy0etmoae.fsf@gitster.g> (raw)
In-Reply-To: <20260729172524.4022621-5-gitster@pobox.com> (Junio C. Hamano's message of "Wed, 29 Jul 2026 10:25:24 -0700")

Junio C Hamano <gitster@pobox.com> writes:

> diff --git a/t/t2207-add-resolved.sh b/t/t2207-add-resolved.sh
> new file mode 100755
> index 0000000000..f88e3f413e
> --- /dev/null
> +++ b/t/t2207-add-resolved.sh
> @@ -0,0 +1,108 @@
> +#!/bin/sh
> +
> +test_description='git add --resolved
> +
> +Test that "git add --resolved" stages conflict-resolved paths and
> +refuses to stage when conflict markers remain.'
> +
> +. ./test-lib.sh
> +
> +test_expect_success 'setup repo' '
> ...
> +	git branch topic &&
> +	echo "ours 1" >file1.txt &&
> +	echo "ours 2" >file2.txt &&
> +	echo "ours 3" >file3.txt &&
> +	git commit -a -m ours &&
> +
> +	git checkout topic &&
> +	echo "theirs 1" >file1.txt &&
> +	echo "theirs 2" >file2.txt &&
> +	echo "theirs 3" >file3.txt &&
> +	git commit -a -m theirs &&
> +
> +	git checkout master
> +'

This will fail with breaking changes.  The last step needs to be

	git checkout @{-1}

to go back to the original branch we were on before checking out the
'topic' branch.

  reply	other threads:[~2026-07-29 22:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-28 21:52 [PATCH 0/4] git add --resolved Junio C Hamano
2026-07-28 21:52 ` [PATCH 1/4] merge-ll: consolidate conflict marker scanning logic Junio C Hamano
2026-07-28 21:52 ` [PATCH 2/4] read-cache: add remove_file_from_index_with_flags() Junio C Hamano
2026-07-28 21:52 ` [PATCH 3/4] add: introduce '--resolved' option Junio C Hamano
2026-07-29  3:28   ` Michael Montalbo
2026-07-29 13:43     ` Junio C Hamano
2026-07-29 13:49       ` Junio C Hamano
2026-07-29 15:01   ` Junio C Hamano
2026-07-28 21:52 ` [PATCH 4/4] read-cache: reindent Junio C Hamano
2026-07-29 17:25 ` [PATCH v2 0/4] git add --resolved Junio C Hamano
2026-07-29 17:25   ` [PATCH v2 1/4] read-cache: reindent Junio C Hamano
2026-07-29 17:25   ` [PATCH v2 2/4] merge-ll: consolidate conflict marker scanning logic Junio C Hamano
2026-07-29 17:25   ` [PATCH v2 3/4] read-cache: add remove_file_from_index_with_flags() Junio C Hamano
2026-07-29 17:25   ` [PATCH v2 4/4] add: introduce '--resolved' option Junio C Hamano
2026-07-29 22:19     ` Junio C Hamano [this message]
2026-07-29 23:41   ` [PATCH v2 0/4] git add --resolved Michael Montalbo

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=xmqqy0etmoae.fsf@gitster.g \
    --to=gitster@pobox.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