Re: [PATCH v3 00/16] pull: default warning improvements
- From
Felipe Contreras <felipe.contreras@gmail.com>
- Date
- Dec 7, 2020, 22:33 UTC
- Message-ID
- <CAMP44s2sDPT8mQqSuUZ7HaN8EBXOdKBkU5t4-1k6EZfmRa0Mow@mail.gmail.com>
- In-Reply-To
- <xmqqwnxt8hev.fsf@gitster.c.googlers.com>
On Mon, Dec 7, 2020 at 2:55 PM Junio C Hamano <gitster@pobox.com> wrote:
Show 17 quoted lines
> > Felipe Contreras <felipe.contreras@gmail.com> writes: > > > It is not a complete solution, but should improve the current situation. > > > > Since v2: > > > > 1. The warning is updated to say "a merge, a rebase, or a fast-forward" > > 2. A suggestion 'If unsure, run "git pull --merge".' is removed > > 3. A new REBASE_DEFAULT is introduced > > 4. Tests are revamped using helpers > > 5. The logic of --merge and --ff-only is updated so one can override the other > > 6. A bunch of commit messages are updated > > 7. A memory inconsistency is fixed > > On what base has this series been built? Applying to 'master' seems > to stop at the "refactor fast-forward check" step.
Ninth batch.
The 'pb/pull-rebase-recurse-submodules' merge is the one causing the conflicts (I think).
-- Felipe Contreras