Date: Thu, 20 Feb 2014 12:08:25 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Allan Jude <freebsd@allanjude.com> Cc: freebsd-doc@freebsd.org Subject: Re: ZFS handbook project patch Message-ID: <alpine.BSF.2.00.1402201201550.71364@wonkity.com> In-Reply-To: <53062F44.1050906@allanjude.com> References: <5305A9A4.1010603@allanjude.com> <20140220.162055.109321178462259649.hrs@allbsd.org> <alpine.BSF.2.00.1402200747110.69044@wonkity.com> <53062F44.1050906@allanjude.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 20 Feb 2014, Allan Jude wrote: > > I've quickly switch those back to <userinput> > > I used simple logic, if talking about a command in a paragraph, use > <command>, when doing it in a <screen> use <userinput>, as in a > paragraph it is usually never more than a subcommand like <command>zfs > send</command> That's correct, IMO. Semantically, command tags could be used inside userinput, but that really does not seem to gain much, and would suggest filenames and other content in <screen> sections would become even more complicated. > Also, I just noticed that a bunch of the stuff from my previous zfs > patch didn't get in (I sent 2, a whitespace and a content patch, and > only the whitespace one got in), so I've included the updated zfs send > stuff as well (how to do replication without root) bcr responded about that, and was waiting for feedback (I think). > IIRC, this means the stuff I wrote for the CARP chapter last week is > wrong with regards to <command> instead of <userinput> ...yes. Fixed.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1402201201550.71364>