diff options
| author | Douglas Gregor <doug.gregor@gmail.com> | 2005-11-05 16:13:37 +0000 |
|---|---|---|
| committer | Douglas Gregor <doug.gregor@gmail.com> | 2005-11-05 16:13:37 +0000 |
| commit | 423012d210a492f6fdd545f2c0a6f1dd2ee2b0a6 (patch) | |
| tree | 431eb2fdb38e6afbc842ae8fe2ef5ae39ab5fad5 | |
| parent | f2e1fe1f860ec3099eff8a1ab043ef819460a810 (diff) | |
| download | boost-423012d210a492f6fdd545f2c0a6f1dd2ee2b0a6.tar.gz | |
Suggest unified diff format
[SVN r31567]
| -rw-r--r-- | more/bugs.htm | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/more/bugs.htm b/more/bugs.htm index b897f111f3..7c1ce18bf4 100644 --- a/more/bugs.htm +++ b/more/bugs.htm @@ -54,7 +54,7 @@ <br> </li> <li>If you have a proposed patch to the code, post it along with your bug - report, preferably in the <em>context diffs</em> format (<code>diff -c</code>); + report, preferably in the <em>unified diffs</em> format (<code>cvs diff -du</code>); if you can, send a patch relative to the current CVS state. A canonical example of creating a patch file follows (let's assume that you've found a bug in the file <code>intentional_bug.hpp</code>:<br> |