Timeline for Move branch pointer to different commit without checkout
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 7, 2020 at 15:21 | comment | added | Keith Russell | I think this should maybe have been a comment on the question, not an answer. (Or maybe it was answering an earlier version of the question?) | |
| Aug 18, 2018 at 9:39 | comment | added | MrMesees |
my preferred method. There should totally be a git repoint <commit> command
|
|
| Aug 12, 2015 at 7:59 | review | Low quality answers | |||
| Aug 12, 2015 at 12:47 | |||||
| Aug 12, 2015 at 7:52 | comment | added | Robert Siemer | @WilsonF, maybe it was nice for you to find this here, but it is not answering the question at all. Maybe it is the answer of some other question, but here it is wrong. | |
| Aug 11, 2015 at 18:57 | comment | added | Wilson F | @Robert: I disagree. The question didn't say how to use it and this does. It was nice not to have to go look for that how. | |
| Apr 20, 2015 at 11:11 | comment | added | Robert Siemer |
Did you noticed that your “answer” does not add anything which is not part of the question already?? – OP said: if it is checked out... you can use git reset --hard ... No need to repeat it here! :-(
|
|
| Apr 8, 2014 at 4:35 | comment | added | a paid nerd |
This is fine if your working tree is clean. If you have lots of staged or unstaged changes, it's probably better to do git update-ref as discussed above.
|
|
| Apr 6, 2014 at 7:41 | comment | added | justingordon | This makes the most sense in that typically one uses HEAD or HEAD^ to move the branch tip back in time. So this is consistent to specify the commit ahead. | |
| Mar 15, 2012 at 18:47 | history | answered | Amiel Martin | CC BY-SA 3.0 |