Re: Re* git pull --rebase should use fast forward merge if possible
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Dec 1, 2016, 18:50 UTC
- Message-ID
- <xmqqoa0va3fw.fsf@gitster.mtv.corp.google.com>
- In-Reply-To
- <CAGZ79kZSEan5uXCUn4iVCWEc9zohMSr+UDyHDyQUHz84H=tR8w@mail.gmail.com>
Stefan Beller <sbeller@google.com> writes:
Show 17 quoted lines
> On Thu, Dec 1, 2016 at 9:59 AM, Junio C Hamano <gitster@pobox.com> wrote: > >> +test_expect_success '--rebase fast forward' ' >> + git reset --hard before-rebase && >> + git checkout -b ff && >> + echo another modification >file && >> + git commit -m third file && >> + >> + git checkout to-rebase && >> + git pull --rebase . ff && >> + test "$(git rev-parse HEAD)" = "$(git rev-parse ff)" && >> + >> + # The above only validates the result. Did we actually bypass rebase? > > Good catch for the test, but I think we can make the sed regexp simpler, as we > can leave out the second "[0-9a-f]"? (git reflog |sed > "s/^[0-9a-f]*/OBJID/" works here)
This mimics the existing tests around there for consistency. Simplifying or cleaning of this test script as a whole is outside the scope.