From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Git Mailing list <git@vger.kernel.org>
Subject: worth enhancing "man git-rebase" to show non-HEAD examples?
Date: Mon, 4 Mar 2019 10:01:32 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.21.1903040955540.16666@localhost.localdomain> (raw)
one of the things i've noticed about the examples in "man
git-rebase" is that they invariably show rebasing relative to a
branch point that has not moved. for example, there's this example:
o---o---o---o---o master
\
o---o---o---o---o next
\
o---o---o topic
with subsequent sample command:
$ git rebase --onto master next topic
sure, that works, but there seem to be no examples that show that this
is a valid starting point as well:
o---o---o---o---o master
\
o---o---o---o---o next
\
o---o---o topic
as in, the examples in that man page could potentially suggest to an
inexperienced reader that the *only* valid situations are rebasing as
long as the other branch has not developed any further. (yes, i
realize that, if you read carefully, it *should* make it clear, but i
think it would be helpful to at least graphically show that
happening.)
thoughts?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca/dokuwiki
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next reply other threads:[~2019-03-04 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 15:01 Robert P. J. Day [this message]
2019-03-05 13:10 ` worth enhancing "man git-rebase" to show non-HEAD examples? Junio C Hamano
2019-03-05 13:16 ` Robert P. J. Day
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.21.1903040955540.16666@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).