From: Hallvard Breien Furuseth <h.b.furuseth@usit.uio.no>
To: git@vger.kernel.org
Subject: Suggestion: rebase [--onto <newbase>] [<upstream>][..[<branch>]]
Date: Tue, 17 Jan 2012 17:44:29 +0100 (CET) [thread overview]
Message-ID: <hbf.20120117gdfh@bombur.uio.no> (raw)
I think
git rebase [--onto <newbase>] [<upstream>][..[<branch>]]
would be a more readable syntax for what rebase is doing. Easier
to see which argument means what without staring at the manpage.
"..[<branch>]" without <upstream> implies --root.
--
Hallvard
next reply other threads:[~2012-01-17 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 16:44 Hallvard Breien Furuseth [this message]
2012-01-17 20:17 ` Suggestion: rebase [--onto <newbase>] [<upstream>][..[<branch>]] Junio C Hamano
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=hbf.20120117gdfh@bombur.uio.no \
--to=h.b.furuseth@usit.uio.no \
--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).