[PATCHv3 1/2] git-rebase.txt: "--onto" option updated
- From
- Lucien Kong <lucien.kong@ensimag.imag.fr>
- Date
- Jun 8, 2012, 14:53 UTC
- Message-ID
- <1339167235-2009-1-git-send-email-Lucien.Kong@ensimag.imag.fr>
- In-Reply-To
- <1338978856-26838-1-git-send-email-Lucien.Kong@ensimag.imag.fr>
The description of the option "--onto" is changed to be consistent with the format of the other options.
Signed-off-by: Lucien Kong <Lucien.Kong@ensimag.imag.fr> Signed-off-by: Valentin Duperray <Valentin.Duperray@ensimag.imag.fr> Signed-off-by: Franck Jonas <Franck.Jonas@ensimag.imag.fr> Signed-off-by: Thomas Nguy <Thomas.Nguy@ensimag.imag.fr> Signed-off-by: Huynh Khoi Nguyen Nguyen <Huynh-Khoi-Nguyen.Nguyen@ensimag.imag.fr> Signed-off-by: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> --- Documentation/git-rebase.txt | 12 +++++++----- 1 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt index 147fa1a..d2a510c 100644 --- a/Documentation/git-rebase.txt +++ b/Documentation/git-rebase.txt @@ -210,11 +210,13 @@ rebase.autosquash:: OPTIONS ------- -<newbase>:: - Starting point at which to create the new commits. If the - --onto option is not specified, the starting point is - <upstream>. May be any valid commit, and not just an - existing branch name. +--onto <newbase>:: + With this option, git rebase takes all commits from <branch>, + that are not in <upstream>, and transplants them on top of + <newbase>. <newbase is the starting point at which to create + the new commits. If the --onto option is not specified, the + starting point is <upstream>. May be any valid commit, and + not just an existing branch name. + As a special case, you may use "A\...B" as a shortcut for the merge base of A and B if there is exactly one merge base. You can
-- 1.7.8