Browse files

doc: document method for reverting commits

PR-URL: #13015
Fixes: #12979
Refs: #4679 (comment)
Reviewed-By: Colin Ihrig <>
Reviewed-By: Rich Trott <>
Reviewed-By: Luigi Pinca <>
Reviewed-By: Benjamin Gruenbaum <>
Reviewed-By: Joyee Cheung <>
Reviewed-By: James M Snell <>
  • Loading branch information...
gibfahn committed May 13, 2017
1 parent fefab90 commit 92f3b301ab706d6254814b3f0a2689a32bbafb01
Showing with 7 additions and 0 deletions.
  1. +7 −0
@@ -252,6 +252,13 @@ not can often be based on many complex factors that are not easily codified. It
is also possible that the breaking commit can be labeled retroactively as a
semver-major change that will not be backported to Current or LTS branches.
##### Reverting commits
Commits are reverted with `git revert <HASH>`, or `git revert <FROM>..<TO>` for
multiple commits. Commit metadata and the reason for the revert should be
appended. Commit message rules about line length and subsystem can be ignored.
A Pull Request should be raised and approved like any other change.
### Deprecations
Deprecation refers to the identification of Public APIs that should no longer

0 comments on commit 92f3b30

Please sign in to comment.