| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The reasoning behind this, is that if we are consistent in our
documentation about the uint*_t stuff, people will be less tempted to
write new code that uses the non-standard types.
I am not going to bump the man page dates, as these changes can be
considered style nits. The meaning of the man pages is unaffected.
MFC after: 1 month
Notes:
svn path=/head/; revision=231564
|
| |
|
|
|
|
|
| |
* Use 'manual' instead of 'man' for consistency.
Notes:
svn path=/head/; revision=121414
|
| |
|
|
| |
Notes:
svn path=/head/; revision=108257
|
| |
|
|
| |
Notes:
svn path=/head/; revision=84306
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
cd src/share; find man[1-9] -type f|xargs perl -pi -e 's/[ \t]+$//'
BTW, what editors are the culprits? I'm using vim and it shows
me whitespace at EOL in troff files with a thick blue block...
Reviewed by: Silence from cvs diff -b
MFC after: 7 days
Notes:
svn path=/head/; revision=79727
|
| |
|
|
| |
Notes:
svn path=/head/; revision=79538
|
| |
|
|
| |
Notes:
svn path=/head/; revision=79454
|
| |
|
|
| |
Notes:
svn path=/head/; revision=76190
|
|
|
device_set_desc_copy.9 and device_get_flags.9.
Notes:
svn path=/head/; revision=51203
|
