cvs commit: src/bin/chio chio.1 src/bin/cp cp.1 src/bin/date
date.1 src/bin/df df.1 src/bin/domainname domainname.1 src/bin/echo
echo.1 src/bin/hostname hostname.1 src/bin/ln ln.1 symlink.7
src/bin/ls ls.1 src/bin/pax pax.1 src/bin/rcp rcp.1 ...
ru at FreeBSD.org
Sat Jul 3 10:47:05 PDT 2004
On Sat, Jul 03, 2004 at 10:50:33AM +0200, Pawel Jakub Dawidek wrote:
> On Fri, Jul 02, 2004 at 09:04:19PM +0000, Ruslan Ermilov wrote:
> +> -operations. This may be used if the operation takes unusually long
> +> +operations.
> +> +This may be used if the operation takes unusually long
> +> because of buggy firmware or the like.
> +> -Change volume tag for an element in the media changer. This command
> +> -is only supported by few media changers. If it is not supported by a
> +> +Change volume tag for an element in the media changer.
> +> +This command
> +> +is only supported by few media changers.
> +> +If it is not supported by a
> +> device, using this command will usually result in an "Invalid Field in
> +> CDB" error message on the console.
> +> -Print the primary volume tag for each loaded medium, if any. The volume
> +> +Print the primary volume tag for each loaded medium, if any.
> +> +The volume
> +> tag is printed as
> [much more]
> Are you planning to join those sentences somehow?
> (i.e. "The volume\ntag is printed as" -> "The volume tag is printed as")
> Or is this ok as it is now?
No, I won't. Yes, it's okay as it's now. What was not okay
is hardcoded sentence breaks. Sometimes, there were two
spaces, but often only one, and sometimes more than two
(not in this particular manpage). It's very very good rule
of thumb to start each new sentence on its own line, so you
never get to worry about them. ;)
ru at FreeBSD.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/cvs-src/attachments/20040703/f9c1198a/attachment.bin
More information about the cvs-src