From: Junio C Hamano <gitster@pobox.com>
To: "John Cai via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Elijah Newren <newren@gmail.com>,
John Cai <johncai86@gmail.com>
Subject: Re: [PATCH v3] merge-ort: initialize repo in index state
Date: Mon, 09 Oct 2023 14:41:53 -0700 [thread overview]
Message-ID: <xmqq4jizxyla.fsf@gitster.g> (raw)
In-Reply-To: <pull.1583.v3.git.git.1696857660374.gitgitgadget@gmail.com> (John Cai via GitGitGadget's message of "Mon, 09 Oct 2023 13:21:00 +0000")
"John Cai via GitGitGadget" <gitgitgadget@gmail.com> writes:
> Fix this by initializing the repository in the index state.
>
> Changes since V2:
>
> * fixed test by using printf instead of echo
Much better than using unportable \n with echo.
> -+ echo "foo\nbar\nbaz" >expect &&
> ++ printf "foo\nbar\nbaz\n" >expect &&
But if we are using printf, it would be easier to read lines
separately, which would look more like
printf "%s\n" foo bar baz >expect
And we have
test_write_lines foo bar baz >expect
to make it even more discoverable.
> + git cat-file -p "$tree:file1" >actual &&
> + test_cmp expect actual
> + )
>
>
> merge-ort.c | 1 +
> t/t4300-merge-tree.sh | 27 +++++++++++++++++++++++++++
> 2 files changed, 28 insertions(+)
>
> diff --git a/merge-ort.c b/merge-ort.c
> index 7857ce9fbd1..36537256613 100644
> --- a/merge-ort.c
> +++ b/merge-ort.c
> @@ -1902,6 +1902,7 @@ static void initialize_attr_index(struct merge_options *opt)
> struct index_state *attr_index = &opt->priv->attr_index;
> struct cache_entry *ce;
>
> + attr_index->repo = opt->repo;
> attr_index->initialized = 1;
>
> if (!opt->renormalize)
> diff --git a/t/t4300-merge-tree.sh b/t/t4300-merge-tree.sh
> index 57c4f26e461..c3a03e54187 100755
> --- a/t/t4300-merge-tree.sh
> +++ b/t/t4300-merge-tree.sh
> @@ -86,6 +86,33 @@ EXPECTED
> test_cmp expected actual
> '
>
> +test_expect_success '3-way merge with --attr-source' '
> + test_when_finished rm -rf 3-way &&
> + git init 3-way &&
> + (
> + cd 3-way &&
> + test_commit initial file1 foo &&
> + base=$(git rev-parse HEAD) &&
> + git checkout -b brancha &&
> + echo bar >>file1 &&
> + git commit -am "adding bar" &&
> + source=$(git rev-parse HEAD) &&
> + git checkout @{-1} &&
> + git checkout -b branchb &&
> + echo baz >>file1 &&
> + git commit -am "adding baz" &&
> + merge=$(git rev-parse HEAD) &&
> + git checkout -b gitattributes &&
> + test_commit "gitattributes" .gitattributes "file1 merge=union" &&
OK, the branch "gitattributes" will be used to drive merge of file1
using the union merge to avoid conflicting.
> + git checkout @{-1} &&
But such attribute will only be available in that branch, not in the
checked out working tree. And then
> + tree=$(git --attr-source=gitattributes merge-tree --write-tree \
> + --merge-base "$base" --end-of-options "$source" "$merge") &&
we use the gitattributes branch as the tree-ish to take the
attribute information from. Makes sense.
> + printf "foo\nbar\nbaz\n" >expect &&
I'll squash in the "test_write_lines" change while queuing.
> + git cat-file -p "$tree:file1" >actual &&
> + test_cmp expect actual
> + )
> +'
> +
> test_expect_success 'file change A, B (same)' '
> git reset --hard initial &&
> test_commit "change-a-b-same-A" "initial-file" "AAA" &&
>
> base-commit: 493f4622739e9b64f24b465b21aa85870dd9dc09
Thanks. Looking good.
next prev parent reply other threads:[~2023-10-09 21:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 15:22 [PATCH] merge-ort: initialize repo in index state John Cai via GitGitGadget
2023-10-05 20:56 ` Junio C Hamano
2023-10-06 5:14 ` Elijah Newren
2023-10-08 16:12 ` John Cai
2023-10-08 16:19 ` [PATCH v2] " John Cai via GitGitGadget
2023-10-09 13:21 ` [PATCH v3] " John Cai via GitGitGadget
2023-10-09 21:41 ` Junio C Hamano [this message]
2023-10-10 15:06 ` John Cai
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=xmqq4jizxyla.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=johncai86@gmail.com \
--cc=newren@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 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 NNTP newsgroup(s).