Re: [PATCH] merge-tree: accept 3 trees as arguments
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jan 31, 2024, 18:14 UTC
- Message-ID
- <xmqqil3974kw.fsf@gitster.g>
- In-Reply-To
- <CABPp-BEDLsVFxjr13XJX9eBLeqD+tRoeHxwJyPsc_+AgGY2GTw@mail.gmail.com>
Elijah Newren <newren@gmail.com> writes:
Show 7 quoted lines
> On Tue, Jan 30, 2024 at 9:15 AM Junio C Hamano <gitster@pobox.com> wrote: >> ... >> > but aaaaaaa and bbbbbbb are not commits that they can find. >> >> Correct. They are what they fed as two trees to be merged, aren't >> they? They (or the script that drives merge-tree and fed these two >> trees) should be recognise these two trees, as long as they are told
I notice "able to" is missing here...
Show 5 quoted lines
>> that is what we show, no? > ... > Yeah, I was worried though that the end user wasn't the one running > the git-merge-tree command, and was trying to dig more into usage > cases.
Sure. That is exactly why I wrote "They (or the script that drives..." above.