Andrew's git
/
gitweb.git
/ diff
summary
|
log
|
commit
| diff |
tree
commit
grep
author
committer
pickaxe
?
re
git-apply(1): document --unidiff-zero
author
Jonas Fonseca
<fonseca@diku.dk>
Sun, 17 Sep 2006 10:55:38 +0000
(12:55 +0200)
committer
Junio C Hamano
<junkio@cox.net>
Sun, 17 Sep 2006 22:08:29 +0000
(15:08 -0700)
Signed-off-by: Jonas Fonseca <fonseca@diku.dk>
Signed-off-by: Junio C Hamano <junkio@cox.net>
Documentation/git-apply.txt
patch
|
blob
|
history
raw
|
patch
|
inline
| side by side (parent:
645927c
)
diff --git
a/Documentation/git-apply.txt
b/Documentation/git-apply.txt
index 0a6f7b32192df8a8a2266b0d302271a62c612b1f..d9137c74898f839a8ee5e79daf1080b2ec882dfd 100644
(file)
--- a/
Documentation/git-apply.txt
+++ b/
Documentation/git-apply.txt
@@
-95,6
+95,16
@@
OPTIONS
context exist they all must match. By default no context is
ever ignored.
context exist they all must match. By default no context is
ever ignored.
+--unidiff-zero::
+ By default, gitlink:git-apply[1] expects that the patch being
+ applied is a unified diff with at least one line of context.
+ This provides good safety measures, but breaks down when
+ applying a diff generated with --unified=0. To bypass these
+ checks use '--unidiff-zero'.
++
+Note, for the reasons stated above usage of context-free patches are
+discouraged.
+
--apply::
If you use any of the options marked "Turns off
'apply'" above, gitlink:git-apply[1] reads and outputs the
--apply::
If you use any of the options marked "Turns off
'apply'" above, gitlink:git-apply[1] reads and outputs the