git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Hallvard Breien Furuseth <h.b.furuseth@usit.uio.no>
Cc: git@vger.kernel.org
Subject: Re: Suggestion: rebase [--onto <newbase>] [<upstream>][..[<branch>]]
Date: Tue, 17 Jan 2012 12:17:21 -0800	[thread overview]
Message-ID: <7vr4yyqe26.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <hbf.20120117gdfh@bombur.uio.no> (Hallvard Breien Furuseth's message of "Tue, 17 Jan 2012 17:44:29 +0100 (CET)")

Hallvard Breien Furuseth <h.b.furuseth@usit.uio.no> writes:

> 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.

I do not offhand see a huge issue if you come up with a patch that allows
users to additionally say:

    $ git rebase upstream..topic
    $ git rebase --onto there upstream..topic

what they express with

    $ git rebase upstream topic
    $ git rebase --onto there upstream topic

today.

However, "git rebase ..topic" to mean "everything down to root from topic"
is not OK; lack of one side in dotted range defaults to HEAD everywhere
else and such a change will introduce a huge discrepancy.

      reply	other threads:[~2012-01-17 20:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-17 16:44 Suggestion: rebase [--onto <newbase>] [<upstream>][..[<branch>]] Hallvard Breien Furuseth
2012-01-17 20:17 ` Junio C Hamano [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=7vr4yyqe26.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=h.b.furuseth@usit.uio.no \
    /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).