From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing list <git@vger.kernel.org>
Subject: Re: [PATCH] doc/rebase: extend examples to show continuing branches
Date: Tue, 5 Mar 2019 09:04:56 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.21.1903050904350.30374@localhost.localdomain> (raw)
In-Reply-To: <xmqqr2blto3k.fsf@gitster-ct.c.googlers.com>
On Tue, 5 Mar 2019, Junio C Hamano wrote:
> "Robert P. J. Day" <rpjday@crashcourse.ca> writes:
>
> > Currently, all of the examples for "man git-rebase" show rebasing from
> > a branch that has had no further development, which might mislead
> > readers into thinking that that is a necessary condition for rebasing,
> > so tweak the examples to show further development on such a branch to
> > clarify that.
>
> We state the status-quo in present tense to start problem
> description, so "Currently" is a noise word you can and should omit.
>
> As I already said, at least one example that rebases a branch that
> was forked from the midpoint of another branch, so the problem
> description is already false. If we apply this patch, do we lose
> all examples that rebase a branch that purely builds on top of the
> tip of another branch? That would also mislead readers into
> thinking that you need to advance the base branch before you can
> rebase the forked branch ;-).
i stand corrected. carry on. :-)
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca/dokuwiki
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
prev parent reply other threads:[~2019-03-05 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 10:48 [PATCH] doc/rebase: extend examples to show continuing branches Robert P. J. Day
2019-03-05 14:03 ` Junio C Hamano
2019-03-05 14:04 ` Robert P. J. Day [this message]
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=alpine.LFD.2.21.1903050904350.30374@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).