Lines Matching refs:then

44 source directory and then strip the first element of the path from filenames
64 know of more than one way to use patch, then you can stop reading this
72 uncompress it before applying it, then you can feed it to patch like this
78 (what I assume you've done in the examples below), then you simply run
126 and have made no modifications yourself to the source files, then you should
128 anyway, then there's a high risk that either your local source tree or the
130 re-downloading the patch and if things are still not OK then you'd be advised
135 If patch stops and presents a "File to patch:" prompt, then patch could not
139 this is the case -- if so, then this is an error by the person who created
143 message similar to that, then it means that patch had to adjust the location
151 If you get a message like "Hunk #3 FAILED at 2387.", then it means that the
158 then patch detected that the change contained in the patch seems to have
161 in error, then just say [n]o and abort this patch. If you applied this patch
163 then you can say [y]es here to make patch revert it for you.
179 So if you get these errors with kernel.org patches then you should probably
190 generate a patch representing the differences between two patches and then
243 If regressions or other serious flaws are found, then a -stable fix patch
280 If no 2.6.x.y kernel is available, then the highest numbered 2.6.x kernel is
293 base 2.6.12 kernel source) and then apply the new 2.6.12.3 patch.