From: Junio C Hamano <gitster@pobox.com>
To: Michele Ballabio <barra_cuda@katamail.com>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH 2/3] document --force-rebase
Date: Wed, 18 Mar 2009 11:38:43 -0700 [thread overview]
Message-ID: <7v7i2mfzgs.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1237399558-27289-2-git-send-email-barra_cuda@katamail.com> (Michele Ballabio's message of "Wed, 18 Mar 2009 19:05:57 +0100")
Michele Ballabio <barra_cuda@katamail.com> writes:
> +-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 looks 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.
next prev parent reply other threads:[~2009-03-18 18:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 18:05 [PATCH 1/3] rebase: fix typo (force_rebas -> force-rebas) Michele Ballabio
2009-03-18 18:05 ` [PATCH 2/3] document --force-rebase Michele Ballabio
2009-03-18 18:38 ` Junio C Hamano [this message]
2009-03-18 18:38 ` Junio C Hamano
2009-03-18 20:53 ` [PATCH v2 " Michele Ballabio
2009-03-18 21:15 ` Johannes Schindelin
2009-03-19 11:01 ` [PATCH " Sverre Rabbelier
2009-03-19 15:28 ` [PATCH v3 " Michele Ballabio
2009-03-19 15:28 ` [PATCH v3 3/3] rebase: add options passed to git-am Michele Ballabio
2009-03-18 18:05 ` [PATCH " Michele Ballabio
2009-03-18 18:41 ` Junio C Hamano
2009-03-18 20:53 ` [PATCH v2 " Michele Ballabio
2009-03-27 18:58 ` [PATCH 1/3] rebase: fix typo (force_rebas -> force-rebas) Michele Ballabio
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v7i2mfzgs.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=barra_cuda@katamail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).