Re: [PATCH 2/3] document --force-rebase

From: Junio C Hamano <gitster@pobox.com>
Date: Mar 18, 2009, 18:38 UTC
Message-ID: <7v63i6fzgc.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <1237399558-27289-2-git-send-email-barra_cuda@katamail.com>

Michele Ballabio <barra_cuda@katamail.com> writes:

Show 6 quoted lines

> +-f::
> +--force-rebase::
> +	Force the rebase even if the current branch is up to date.
> +	Normally, if the current branch is up to date, the rebase is
> +	aborted.
> +

For the sake of brevity we say "up to date" in the error message from the command, but for people who look up the manual to figure out why their rebase is not rebasing with that error message, we may want to explain what the phrase means in this context. E.g.

	... even if the branch is a descendant of the commit you are
	rebasing onto.  Normally the command will exit with a message
	"Current branch is up to date" in such a situation.