* HACKING: use shorter "-1" (over HEAD~1) with git format-patch

diff --git a/HACKING b/HACKING
index 07026b11c63ebebe39e231e94245e842e6b3f69c..457048e60206d20808c00d6588be02a7e8af039c 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -69,7 +69,7 @@ Once your change is committed, you can create a proper patch that includes
 a log message and authorship information as well as any permissions
 changes.  Use this command to save that single, most-recent change set:
 
 a log message and authorship information as well as any permissions
 changes.  Use this command to save that single, most-recent change set:
 

-  git format-patch --stdout HEAD~1 > DIFF
+  git format-patch --stdout -1 > DIFF

 
 The trouble with this approach is that you've just checked in a change
 (remember, it's only local) on the "master" branch, and that's where new
 
 The trouble with this approach is that you've just checked in a change
 (remember, it's only local) on the "master" branch, and that's where new


@@ -185,7 +185,7 @@ It's easy to adjust:
 
   edit your files # this can include running "git add NEW" or "git rm BAD"
   git commit --amend -e -a
 
   edit your files # this can include running "git add NEW" or "git rm BAD"
   git commit --amend -e -a

-  git format-patch --stdout HEAD~1 > your-branch.diff
+  git format-patch --stdout -1 > your-branch.diff

 
 That replaces the most recent change-set with the revised one.
 
 
 That replaces the most recent change-set with the revised one.