#git bot interface

History of !revert

• That's a rather ambiguous question... options: a) make a commit that "undoes" the effects of an earlier commit [man git-revert]; b) discard uncommitted changes in the working tree [git reset --hard]; c) undo committing [git reset --soft HEAD^]; d) restore staged versions of files [git checkout -p]; e) move the current branch to a different point(possibly losing commits)[git reset --hard $COMMIT]?
  By jast at 2013-06-14 12:15:02
• "Revert" is a heavily overloaded term -- Do you mean: a) make a commit that "undoes" the effects of an earlier commit [man git-revert]; b) discard uncommitted changes in the working tree [git reset --hard]; c) undo committing [git reset --soft HEAD^]; d) restore staged versions of files [git checkout -p]; e) move the current branch to a different point(possibly losing commits)[git reset --hard $COMMIT]?
  By EugeneKay at 2012-10-22 23:21:06
• "Revert" is a heavily overloaded term. Do you mean: a) make a commit that "undoes" the effects of an earlier commit [man git-revert]; b) discard the uncommitted changes in the working tree [no turning back: git reset --hard]; c) undo committing [git reset --soft HEAD^, but type !rewriting_public_history]; d) restore staged versions of files [git checkout -p]?
  By jast at 2012-08-14 19:38:08
• "Revert" is a heavily overloaded term. Do you mean: a) make a commit that "undoes" the effects of an earlier commit [man git-revert]; b) discard the uncommitted changes in the working tree [no turning back: git reset --hard]; c) undo committing [git reset --soft HEAD^, but type !rewriting_public_history] ; d) restore staged versions of files [git checkout -p]?
  By jast at 2012-08-14 19:37:58
• "Revert" is a heavily overloaded term. Do you mean: a) make a commit that "undoes" the effects of an earlier commit [man git-revert]; b) discard the uncommitted changes in the working tree [no turning back: git reset --hard]; c) undo committing [git reset --soft HEAD^, but type !rewriting_public_history] ?
  By jast at 2012-08-14 19:35:51
• "Revert" is a heavily overloaded term. Do you mean: a) make a commit that "undoes" the effects of an earlier commit [man git-revert]; b) discard the uncommitted changes in the working tree [git checkout -- .]; c) undo committing [git reset --soft HEAD^, but type !rewriting_public_history] ?
  By charon at 2012-02-02 15:43:59
• "Revert" is a heavily overloaded term. Do you mean: a) make a commit that "undoes" the effects of an earlier commit [man git-revert]; b) discard the uncommitted changes in the working tree [git checkout -- .]; c) undo committing [git reset HEAD^, but type !rewriting_public_history] ?
  By charon at 2012-02-02 15:43:05
• "Revert" is a heavily overloaded term. Do you mean: a) make a commit that "undoes" the effects of an earlier commit [man git-revert]; b) discard the uncommitted changes in the working tree [git checkout -- .]; c) undo committing [type !fixup] ?
  By charon at 2012-02-02 15:35:33
• Revert is a heavily overloaded term in version control. Do you mean: a) make a commit that "undoes" the effects of an earlier commit [man git-revert]; b) discard the uncommitted changes in the working tree [git checkout -- .]; c) undo committing [type !fixup] ?
  By charon at 2012-02-02 15:35:06