contrib: completion: fix 'eread()' namespace

Otherwise it might collide with a function of the same name in the
user's environment.

Suggested-by: SZEDER Gábor <szeder@ira.uka.de>
Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>
rebase: disable fork-point by default

It is possible that the upstream branch was at some point in the wrong
commit. The user might do 'git reset --hard' to restore that branch to
the right place, the wrong location is already in the reflog.

If the user tries to do a rebase without arguments the fork-point
feature will be used automatically and the wrong point in the reflog
used as one of the possible heads to check for bases.

This is especially bad when upstream was already in the same place as
the current branch (say upstream was fast-forwarded to topic by
mistake), in which case the rebase would silently ignore all the commits
and reset to upstream. The user would wonder what happened with his
commits, or worst; assume they were already in upstream.

This is a very bad situation we should try to avoid.

We cannot rely on the fact that the reflog will always contain only
good heads, therefore the fork-point should be disabled by default.

The fork-point feature is still useful, but it should be enabled
manually, only when the user knows what he is doing, and that all the
points in the reflog of the upstream branch are desirable.

Signed-off-by: Felipe Contreras <felipe.contreras@gmail.com>