Create section: drop commit with git rebase -i

Fixes #824

Author: HonkingGoose

book/07-git-tools/sections/rewriting-history.asc

@@ -299,6 +299,34 @@ This changes the SHA-1s of the three most recent commits in your list, so make s
 Notice that the last commit (`f7f3f6d`) in the list is unchanged.
 Despite this commit being shown in the script, because it was marked as ``pick'' and was applied prior to any rebase changes, Git leaves the commit unmodified.
 
+==== Deleting a commit
+
+If you want to get rid of a commit, you can delete it using the `rebase -i` script.
+In the list of commits, put the word ``drop'' before the commit you want to delete:
+
+[source,console]
+----
+pick 461cb2a This commit is OK
+drop 5aecc10 This commit is broken
+----
+
+[CAUTION]
+====
+Do not delete/drop a commit that other commits depend on!
+It's a bad idea to drop the first commit in the `rebase -i` script list.
+The following commits depend on the first commit being present, as the root of all changes that follow.
+====
+
+Avoid doing this:
+[source,console]
+----
+drop 5aecc10 This commit is broken
+pick c6be4c9 This commit is OK but depends on changes made in 5aecc10
+----
+
+Git will complain about the broken state, and ask you to resolve the conflicts manually.
+You can also just back out of the rebase by using `git rebase --abort`.
+
 [NOTE]
 ====
 Drew DeVault made a practical hands-on guide with exercises to learn how to use `git rebase`.