/openbsd/usr.bin/true/ |
H A D | true.1 | d406b0bb Tue Jan 06 23:56:18 GMT 2009 jmc <jmc@openbsd.org> i saw the previous was wrong as soon as i committed it: put the built-in blurb in STANDARDS; we did once have a COMPATIBILITY section which we merged with STANDARDS, so i think this is appropriate. it certainly feels better than adding single sentences randomly to the end of text bodies.
|
/openbsd/usr.bin/false/ |
H A D | false.1 | d406b0bb Tue Jan 06 23:56:18 GMT 2009 jmc <jmc@openbsd.org> i saw the previous was wrong as soon as i committed it: put the built-in blurb in STANDARDS; we did once have a COMPATIBILITY section which we merged with STANDARDS, so i think this is appropriate. it certainly feels better than adding single sentences randomly to the end of text bodies.
|
/openbsd/usr.bin/nohup/ |
H A D | nohup.1 | d406b0bb Tue Jan 06 23:56:18 GMT 2009 jmc <jmc@openbsd.org> i saw the previous was wrong as soon as i committed it: put the built-in blurb in STANDARDS; we did once have a COMPATIBILITY section which we merged with STANDARDS, so i think this is appropriate. it certainly feels better than adding single sentences randomly to the end of text bodies.
|
/openbsd/usr.bin/nice/ |
H A D | nice.1 | d406b0bb Tue Jan 06 23:56:18 GMT 2009 jmc <jmc@openbsd.org> i saw the previous was wrong as soon as i committed it: put the built-in blurb in STANDARDS; we did once have a COMPATIBILITY section which we merged with STANDARDS, so i think this is appropriate. it certainly feels better than adding single sentences randomly to the end of text bodies.
|
/openbsd/bin/pwd/ |
H A D | pwd.1 | d406b0bb Tue Jan 06 23:56:18 GMT 2009 jmc <jmc@openbsd.org> i saw the previous was wrong as soon as i committed it: put the built-in blurb in STANDARDS; we did once have a COMPATIBILITY section which we merged with STANDARDS, so i think this is appropriate. it certainly feels better than adding single sentences randomly to the end of text bodies.
|
/openbsd/sbin/mknod/ |
H A D | mknod.8 | d406b0bb Tue Jan 06 23:56:18 GMT 2009 jmc <jmc@openbsd.org> i saw the previous was wrong as soon as i committed it: put the built-in blurb in STANDARDS; we did once have a COMPATIBILITY section which we merged with STANDARDS, so i think this is appropriate. it certainly feels better than adding single sentences randomly to the end of text bodies.
|
/openbsd/bin/echo/ |
H A D | echo.1 | d406b0bb Tue Jan 06 23:56:18 GMT 2009 jmc <jmc@openbsd.org> i saw the previous was wrong as soon as i committed it: put the built-in blurb in STANDARDS; we did once have a COMPATIBILITY section which we merged with STANDARDS, so i think this is appropriate. it certainly feels better than adding single sentences randomly to the end of text bodies.
|
/openbsd/usr.bin/time/ |
H A D | time.1 | d406b0bb Tue Jan 06 23:56:18 GMT 2009 jmc <jmc@openbsd.org> i saw the previous was wrong as soon as i committed it: put the built-in blurb in STANDARDS; we did once have a COMPATIBILITY section which we merged with STANDARDS, so i think this is appropriate. it certainly feels better than adding single sentences randomly to the end of text bodies.
|
/openbsd/usr.bin/which/ |
H A D | which.1 | d406b0bb Tue Jan 06 23:56:18 GMT 2009 jmc <jmc@openbsd.org> i saw the previous was wrong as soon as i committed it: put the built-in blurb in STANDARDS; we did once have a COMPATIBILITY section which we merged with STANDARDS, so i think this is appropriate. it certainly feels better than adding single sentences randomly to the end of text bodies.
|
/openbsd/bin/kill/ |
H A D | kill.1 | d406b0bb Tue Jan 06 23:56:18 GMT 2009 jmc <jmc@openbsd.org> i saw the previous was wrong as soon as i committed it: put the built-in blurb in STANDARDS; we did once have a COMPATIBILITY section which we merged with STANDARDS, so i think this is appropriate. it certainly feels better than adding single sentences randomly to the end of text bodies.
|
/openbsd/bin/test/ |
H A D | test.1 | d406b0bb Tue Jan 06 23:56:18 GMT 2009 jmc <jmc@openbsd.org> i saw the previous was wrong as soon as i committed it: put the built-in blurb in STANDARDS; we did once have a COMPATIBILITY section which we merged with STANDARDS, so i think this is appropriate. it certainly feels better than adding single sentences randomly to the end of text bodies.
|