From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Alter git-rebase command line options.
Date: Wed, 26 Apr 2006 14:30:47 +0200 [thread overview]
Message-ID: <e2np4p$b9a$1@sea.gmane.org> (raw)
In-Reply-To: BAYC1-PASMTP0659C709B7FFCB63182FE1AEBC0@CEZ.ICE
sean wrote:
> git rebase [--branch <branch>] <newbase>
> git rebase --continue
> git rebase --abort
>
> Add "--continue" to restart the rebase process after
> manually resolving conflicts. The user is warned if
> there are still differences between the index and the
> working files.
>
> Add "--abort" to restore the original branch, and
> remove the .dotest working files.
Very nice.
> SYNOPSIS
> --------
> -'git-rebase' [--onto <newbase>] <upstream> [<branch>]
> +'git-rebase' [--branch <branch>] <newbase>
> +
> +'git-rebase' --continue
> +
> +'git-rebase' --abort
>
> DESCRIPTION
> -----------
> -git-rebase applies to <upstream> (or optionally to <newbase>) commits
> -from <branch> that do not appear in <upstream>. When <branch> is not
> -specified it defaults to the current branch (HEAD).
> +git-rebase replaces <branch> with a new branch of the same name having
> +a HEAD of <newbase>. It then attempts to make a new commit for each
> +commit from the original <branch> that does not yet exist in this new
> +<branch>.
What about 'git-rebase --onto <newbase> <upstream> <branch>' three options
version?
--
Jakub Narebski
Warsaw, Poland
next prev parent reply other threads:[~2006-04-26 12:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060426075118.65876315.seanlkml@sympatico.ca>
2006-04-26 11:51 ` [PATCH] Alter git-rebase command line options sean
2006-04-26 12:30 ` Jakub Narebski [this message]
[not found] ` <20060426090447.0053165c.seanlkml@sympatico.ca>
2006-04-26 13:04 ` sean
[not found] ` <20060426104938.1ff14b2b.seanlkml@sympatico.ca>
2006-04-26 14:49 ` [PATCH] Add --continue and --abort options to git-rebase sean
2006-04-26 20:05 ` Junio C Hamano
[not found] ` <20060427014237.6f7e5f8b.seanlkml@sympatico.ca>
2006-04-27 5:42 ` sean
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='e2np4p$b9a$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.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 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).