Lines Matching refs:it

24 To correctly apply a patch you need to know what base it was generated from
33 (or patch) file and makes the changes to the source tree described in it.
39 kernel source directories it was generated against (or some other directory
45 in the patch file when applying it (the -p1 argument to `patch' does this).
51 You can revert (undo) it like this:
72 uncompress it before applying it, then you can feed it to patch like this
77 If you wish to uncompress the patch file by hand first before applying it
95  When patch applies a patch file it attempts to verify the sanity of the
101 If patch encounters something that doesn't look quite right it has two
102 options. It can either refuse to apply the changes and abort or it can try
110 everything looks good it has just moved up or down a bit, and patch will
113 Whenever patch applies a patch that it had to modify a bit to make it fit
114 it'll tell you about it by saying the patch applied with 'fuzz'.
115 You should be wary of such changes since even though patch probably got it
116 right it doesn't /always/ get it right, and the result will sometimes be
119 When patch encounters a change that it can't fix up with fuzz it rejects it
122 go fix it up by hand if you wish.
143 message similar to that, then it means that patch had to adjust the location
144 of the change (in this example it needed to move 7 lines from where it
145 expected to make the change to make it fit).
151 If you get a message like "Hunk #3 FAILED at 2387.", then it means that the
160 If you actually did apply this patch previously and you just re-applied it
162 previously and actually intended to revert it, but forgot to specify -R,
163 then you can say [y]es here to make patch revert it for you.
166 the patch will in fact apply it.
170 the file you fed to it. Either your download is broken, you tried to feed
171 patch a compressed patch file without uncompressing it first, or the patch
193 step. The -z flag to interdiff will even let you feed it patches in gzip or
313 stable kernel, so it is important that it be tested by as many people as
391 Once a patch has proved its worth in -mm for a while Andrew pushes it on to
394 Although it's encouraged that patches flow to Linus via the -mm tree, this