summaryrefslogtreecommitdiff
path: root/Documentation/SubmittingPatches
diff options
context:
space:
mode:
authorJunio C Hamano <junkio@cox.net>2007-05-25 02:25:25 (GMT)
committerJunio C Hamano <junkio@cox.net>2007-05-25 04:36:53 (GMT)
commit59c8e2cb2aee2e4eb75007602b264bc4e7928bc0 (patch)
tree41c2f6494ee7e95ba5676e1baf55ed77ace73ede /Documentation/SubmittingPatches
parentd45cc6e2670bbfecb16c608a2bb0e3f358a9ece7 (diff)
downloadgit-59c8e2cb2aee2e4eb75007602b264bc4e7928bc0.zip
git-59c8e2cb2aee2e4eb75007602b264bc4e7928bc0.tar.gz
git-59c8e2cb2aee2e4eb75007602b264bc4e7928bc0.tar.bz2
Remove git-applypatch
The previous one removed git-applymbox, which was the sole user of this tool. Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'Documentation/SubmittingPatches')
-rw-r--r--Documentation/SubmittingPatches4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index b94d9a8..b5f2ecd 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -239,7 +239,7 @@ One test you could do yourself if your MUA is set up correctly is:
$ git fetch http://kernel.org/pub/scm/git/git.git master:test-apply
$ git checkout test-apply
$ git reset --hard
- $ git applymbox a.patch
+ $ git am a.patch
If it does not apply correctly, there can be various reasons.
@@ -247,7 +247,7 @@ If it does not apply correctly, there can be various reasons.
does not have much to do with your MUA. Please rebase the
patch appropriately.
-* Your MUA corrupted your patch; applymbox would complain that
+* Your MUA corrupted your patch; "am" would complain that
the patch does not apply. Look at .dotest/ subdirectory and
see what 'patch' file contains and check for the common
corruption patterns mentioned above.