Skip to content

Comments about command lines ("Submitting a Patch" page) #3458

Closed
@alexislefebvre

Description

@alexislefebvre

Implicit option name

See this portion of text found here:

$ git rebase -f upstream/master
$ git push -f origin BRANCH_NAME

when doing a push --force, always specify the branch name explicitly to avoid messing other branches in the repo (--force tells Git that you really want to mess with things so do it carefully).

Advanced users may know that -f is equivalent to --force, but this is not clear for users unaware of this shortcut to the --force command.

Missing reference

See this sentence found here:

$ git rebase -i upstream/master
$ git push -f origin BRANCH_NAME

The number 3 here must equal the amount of commits in your branch. [...]

The start of the sentence makes a reference about a number which is not present is the 2 command lines above. The number was present in 2.2 version:

$ git rebase -i HEAD~3
$ git push -f origin BRANCH_NAME

The number 3 here must equal the amount of commits in your branch. [...]

Since I don't know if the change from HEAD~3 (in 2.2) to upstream/master (in 2.3) is correct, I won't make a pull request.

Broken paragraph (already fixed in #3455)

Just look at the end of the page, the text after just is in a separated block. It was ok in 2.2 version.

Q A
Doc fix? yes
New docs? no
Applies to 2.3+
Fixed tickets -

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions