Skip to content

There is a small inconsistency in deprecation message with "git reset --mixed" #1187

Closed

Description

Currently working my way through "Reset Demystified", and I would like to draw the Court's attention to an exchange I had a couple months back on the Git ML:
https://marc.info/?l=git&m=154428515423409&w=2
where, even though "--mixed" is the default mode for reset, specifying that mode versus not specifying it generates different behaviour, even if the end result is equivalent.
Not sure what to do about this, is it worth explaining?

Activity

  1. ben commented on Feb 17, 2019

    @ben
    Member

    I don't think so. The only discernible difference in the behavior is the deprecation warning, which few users should run into.

    The distinction Junio is drawing there is purely an implementation one, and in my view, if the end behavior is the same, the user shouldn't have to care.

  2. ghost closed this as completedon Feb 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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