summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJim Meyering <meyering@redhat.com>2008-06-26 21:03:55 +0200
committerJim Meyering <meyering@redhat.com>2008-06-26 21:08:22 +0200
commit556fbb57216b119155cdda824c98dc579b8121c8 (patch)
treeefc7c8ddd8672c55c6af8b9e7f3efd4764924639
parentb1a1c9ee068ab41c08cf289b85981985412b5dd2 (diff)
downloadcoreutils-556fbb57216b119155cdda824c98dc579b8121c8.tar.xz
* HACKING: use shorter "-1" (over HEAD~1) with git format-patch
-rw-r--r--HACKING4
1 files changed, 2 insertions, 2 deletions
diff --git a/HACKING b/HACKING
index 07026b11c..457048e60 100644
--- 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:
- 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
@@ -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
- 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.