* Possible bug in `git reset` in 1.9
@ 2014-06-18 17:01 James Coleman
2014-06-18 17:20 ` Possible bug in `gitreset` " James Coleman
0 siblings, 1 reply; 2+ messages in thread
From: James Coleman @ 2014-06-18 17:01 UTC (permalink / raw)
To: git
Suppose I have the following branches:
* branch-1 with commits A - B - C
* branch-2 with commits A - B - C - D
Prior to version 1.9, running `git reset --hard D` while branch-1 is
checked out will result in changing the current branch HEAD to commit
hash D (essentially what update-ref would do).
In 1.9.1 (I haven't tested on 1.9.0 yet), however, running `git reset
--hard D` while branch-1 is checked out will result in the following
output:
$ fatal: Could not parse object 'D'
I assume that this is not an expected change as nothing about changes
to the reset command is present in the change log for 1.9.0 or 1.9.0.
Is this a bug or was the previous behavior unexpected as well? Either
way, it's a regression in terms of what can be expected based on
previous version.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Possible bug in `gitreset` in 1.9
2014-06-18 17:01 Possible bug in `git reset` in 1.9 James Coleman
@ 2014-06-18 17:20 ` James Coleman
0 siblings, 0 replies; 2+ messages in thread
From: James Coleman @ 2014-06-18 17:20 UTC (permalink / raw)
To: git
Followup on this, it looks like the local repository actually didn't contain
branch-2. So this doesn't appear to be an issue.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-06-18 17:25 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-06-18 17:01 Possible bug in `git reset` in 1.9 James Coleman
2014-06-18 17:20 ` Possible bug in `gitreset` " James Coleman
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).