[PATCH v4 3/5] doc: git rebase: clarify arguments syntax
- From
Julia Evans via GitGitGadget <gitgitgadget@gmail.com>
- Date
- Aug 9, 2025, 01:14 UTC
- Message-ID
- <fe9e161a51b2c514287762ea841e5fee7f578ffc.1754702057.git.gitgitgadget@gmail.com>
- In-Reply-To
- <pull.1949.v4.git.1754702057.gitgitgadget@gmail.com>
From: Julia Evans <julia@jvns.ca>
Remove duplicate explanation of `git rebase <upstream> <branch>` which is already explained above.
Signed-off-by: Julia Evans <julia@jvns.ca> --- Documentation/git-rebase.adoc | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/Documentation/git-rebase.adoc b/Documentation/git-rebase.adoc index e30b9535fff1..914f743ae00f 100644 --- a/Documentation/git-rebase.adoc +++ b/Documentation/git-rebase.adoc @@ -59,12 +59,7 @@ one of these things: git rebase --skip - -If `<branch>` is specified, `git rebase` will perform an automatic -`git switch <branch>` before doing anything else. Otherwise -it remains on the current branch. - -If `<upstream>` is not specified, the upstream configured in +If you don't specify an `<upstream>` to rebase onto, the upstream configured in `branch.<name>.remote` and `branch.<name>.merge` options will be used (see linkgit:git-config[1] for details) and the `--fork-point` option is assumed. If you are currently not on any branch or if the current
-- gitgitgadget