All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: Matthew Brett <matthew.brett@gmail.com>,
	Git Mailing List <git@vger.kernel.org>,
	Reuben Thomas <rrt@sc3d.org>
Subject: Re: Advice on edits to git-rebase man page
Date: Thu, 05 Feb 2015 13:29:45 -0800	[thread overview]
Message-ID: <xmqqmw4sjbcm.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <vpq1tm412dk.fsf@anie.imag.fr> (Matthieu Moy's message of "Thu, 05 Feb 2015 22:20:55 +0100")

Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:

> Junio C Hamano <gitster@pobox.com> writes:
>
>> Perhaps something like this instead?
>>
>>     git-rebase - Rebuild a branch on top of a different commit
>
> I would say "Replay history on top of a different commit" instead.
> "Rebuild" may be misleading (it's not "build" as in "compile & link"),
> and the rebased history does not technically have to be a branch.

I am fine if the description were "replay history and repoint the
branch tip to the result"; the fact that branch tip moves is an
important part of the semantics of the command.

Otherwise, you cannot cleanly capture why we have rebase and
cherry-pick (which can do ranges these days).

  reply	other threads:[~2015-02-05 21:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04 20:21 Advice on edits to git-rebase man page Matthew Brett
2015-02-05 10:44 ` Matthieu Moy
2015-02-05 18:58   ` Junio C Hamano
2015-02-05 21:20     ` Matthieu Moy
2015-02-05 21:29       ` Junio C Hamano [this message]
2015-02-18 18:59     ` Matthew Brett
2015-02-23 18:24       ` Matthew Brett

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=xmqqmw4sjbcm.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=git@vger.kernel.org \
    --cc=matthew.brett@gmail.com \
    --cc=rrt@sc3d.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.