{"thread":{"id":"36948","subject":"Possible bug in `git reset` in 1.9","startedAt":"2014-06-18T17:01:59Z","lastAt":"2014-06-18T17:20:37Z","messageCount":2,"participants":["James Coleman"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"244519","messageId":"CAAaqYe9FcjE9v+bkcnkPim8ntFvbUy72dJJCGs7974dq_9eSOw@mail.gmail.com","threadId":"36948","inReplyTo":null,"subject":"Possible bug in `git reset` in 1.9","fromName":"James Coleman","fromEmail":"jtc331@gmail.com","sentAt":"2014-06-18T17:01:59Z","receivedAt":"2014-06-18T17:01:59Z","isPatch":false,"sender":{"key":"jtc331@gmail.com","avatar":null},"body":"Suppose I have the following branches:\n* branch-1 with commits A - B - C\n* branch-2 with commits A - B - C - D\n\nPrior to version 1.9, running `git reset --hard D` while branch-1 is\nchecked out will result in changing the current branch HEAD to commit\nhash D (essentially what update-ref would do).\n\nIn 1.9.1 (I haven't tested on 1.9.0 yet), however, running `git reset\n--hard D` while branch-1 is checked out will result in the following\noutput:\n$ fatal: Could not parse object 'D'\n\nI assume that this is not an expected change as nothing about changes\nto the reset command is present in the change log for 1.9.0 or 1.9.0.\nIs this a bug or was the previous behavior unexpected as well? Either\nway, it's a regression in terms of what can be expected based on\nprevious version.\n"},{"id":"244542","messageId":"loom.20140618T191909-464@post.gmane.org","threadId":"36948","inReplyTo":"CAAaqYe9FcjE9v+bkcnkPim8ntFvbUy72dJJCGs7974dq_9eSOw@mail.gmail.com","subject":"Re: Possible bug in `gitreset` in 1.9","fromName":"James Coleman","fromEmail":"jtc331@gmail.com","sentAt":"2014-06-18T17:20:37Z","receivedAt":"2014-06-18T17:20:37Z","isPatch":false,"sender":{"key":"jtc331@gmail.com","avatar":null},"body":"Followup on this, it looks like the local repository actually didn't contain\nbranch-2. So this doesn't appear to be an issue.\n"}]}