From: Jonathan Nieder <jrnieder@gmail.com>
To: Jonathon Mah <me@JonathonMah.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: RFC: Renaming "git rebase --onto"
Date: Mon, 30 Mar 2015 14:03:19 -0700 [thread overview]
Message-ID: <20150330210319.GC22844@google.com> (raw)
In-Reply-To: <05D9209E-FAA2-44C8-9B98-B00997AF5779@JonathonMah.com>
Jonathon Mah wrote:
> Personally, I understand “git-rebase --onto new-base old-base” as
> meaning “rebase from old-base to new-base”. Some prepositions that
> might make this clearer:
>
> $ git rebase --from old-base new-base # “Rebase HEAD onto new-base, from old-base"
Would having an option name for the old-base argument help?
For example:
git rebase --old-base=<old-base> --onto=<new-base> <branch>
?
Thanks,
Jonathan
next prev parent reply other threads:[~2015-03-30 21:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 20:49 RFC: Renaming "git rebase --onto" Jonathon Mah
2015-03-30 21:03 ` Jonathan Nieder [this message]
2015-03-30 21:12 ` Junio C Hamano
2015-04-02 16:40 ` Michael J Gruber
2015-03-30 21:53 ` Max Kirillov
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=20150330210319.GC22844@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=me@JonathonMah.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).