public inbox for developer@lists.illumos.org (since 2011-08)
 help / color / mirror / Atom feed
From: Robert Mustacchi <rm@joyent.com>
To: Yuri Pankov <yuri.pankov@nexenta.com>,
	illumos-developer <developer@lists.illumos.org>
Subject: Re: [developer] [REVIEW] (again) 5713, 5714, 5715 updates to share man pages
Date: Wed, 29 Jun 2016 16:28:49 -0700	[thread overview]
Message-ID: <1293b549-293d-7c55-b285-0b518035d902@joyent.com> (raw)
In-Reply-To: <108d5d95-1c35-1119-f862-c75c4f70fb03@nexenta.com>

On 6/28/16 7:58 , Yuri Pankov wrote:
> On Tue, 21 Jun 2016 16:50:41 -0700, Robert Mustacchi wrote:
>> On 6/19/16 7:38 , Yuri Pankov wrote:
>>> issue: https://www.illumos.org/issues/5713
>>> issue: https://www.illumos.org/issues/5714
>>> issue: https://www.illumos.org/issues/5715
>>> webrev: http://www.xvoid.org/illumos/webrev/il-man-share/
>>>
>>> The changes are tied together thus one webrev.
>>>
>>> - remove NFS/SMB options and access_list description from sharemgr(1M)
>>> - remove access_list description from share_nfs(1M)
>>> - add share_smb(1M) describing SMB options
>>> - add shareacl(4) describing access_list format
>>
>> I started going through this and I'm a bit confused. Your sharemgr(1M)
>> in sdiffs doesn't look anything like the one currently in the gate. What
>> was this built against? I have more specific comments below:
> 
> Sorry, forgot the conversion diff, which also moved the examples to
> where they belong - I understand that this makes the review harder, and
> I'm sorry for that, but I did that work long ago and just don't want to
> see it got lost.
> 
> http://www.xvoid.org/illumos/webrev/il-man-sharemgr-mdoc/

For what it's worth, it wasn't just the example shuffling, but also the
reordering and the options changing a bunch. I've tried to go through
this as best as I can.

I don't quite get why -h is going away, especially when this is noted as
committed.

Would it be possible to make sure that we have references to the
examples. e.g. see example n.

sharemgr unset used to take a [-s sharepath] option in the long form. It
doesn't seem to in the synopsis or otherwise anymore in the new form;
however, you still reference the -s option in the description. What
should it be?

Robert


  reply	other threads:[~2016-06-29 23:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-19 14:38 Yuri Pankov
2016-06-21 23:50 ` [developer] " Robert Mustacchi
2016-06-28 14:58   ` Yuri Pankov
2016-06-29 23:28     ` Robert Mustacchi [this message]
2024-09-21 20:53 ` [developer] share_smb(8)? (Was: 5713, 5714, 5715 updates to share man pages) Gordon Ross

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1293b549-293d-7c55-b285-0b518035d902@joyent.com \
    --to=rm@joyent.com \
    --cc=developer@lists.illumos.org \
    --cc=yuri.pankov@nexenta.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).