Matthieu Moy <Matthieu.Moy@xxxxxxxxxxxxxxx> writes:
> Short answer: trust me, without the patch, you get the non-fast
> forward (and valgrind tells you about conditional jump on
> uninitialized value), with, you don't ;-).
I understand valgrind one; I can trace the codepath with eyeballs without
it, and that is why I said it looks correct to begin with.
My puzzlement was that the following in the log message did not seem to
reproduce for me:
... where "git push ... nonexisting-branch" was complaining about
non-fast forward.
I would be eventually writing an entry in the Release Notes about this
fix, and I do not want to say:
"git push $there no-such-ref" incorrectly said no-such-ref does not
fast forward; fixed.
when I know that command line would produce something entirely different
error.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html