Lines Matching refs:when

81 changes would normally appear when you pull the latest from "upstream".
111     Be careful to run "git pull" only when on the "master" branch,
112     not when on a branch.  With newer versions of git, you can't cause
219 to write a few lines of prose describing the change, when the summary
251 Omit the curly braces around an "if", "while", "for" etc. body only when
279 There is one exception: when the second body line is not at the same
308 However, there is one exception in the other direction, when even a
309 one-line block should have braces.  That occurs when that one-line,
324 This is preferred, especially when the multi-line body is more than a
326 an if-then-else block when the simpler block occurs first, rather than
502 ensures that the build completes with no warnings when using a certain
600 uncover when you improve test coverage, and even if you don't find