# Suggestion: rebase [--onto <newbase>] [<upstream>][..[<branch>]]

2 messages from 2012-01-17 to 2012-01-17. Participants: Hallvard Breien Furuseth, Junio C Hamano.
Thread: https://gitlist.dev/t/29384

## Hallvard Breien Furuseth, 2012-01-17 16:44

Subject: Suggestion: rebase [--onto <newbase>] [<upstream>][..[<branch>]]
Message-ID: <hbf.20120117gdfh@bombur.uio.no>
URL: https://gitlist.dev/e/hbf.20120117gdfh%40bombur.uio.no

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

-- 
Hallvard

```

## Junio C Hamano, 2012-01-17 20:17

Subject: Re: Suggestion: rebase [--onto <newbase>] [<upstream>][..[<branch>]]
Message-ID: <7vr4yyqe26.fsf@alter.siamese.dyndns.org>
URL: https://gitlist.dev/e/7vr4yyqe26.fsf%40alter.siamese.dyndns.org
In-Reply-To: <hbf.20120117gdfh@bombur.uio.no>

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

```