public inbox for developer@lists.illumos.org (since 2011-08)
 help / color / mirror / Atom feed
From: Olaf Bohlen <olbohlen@eenfach.de>
To: illumos-developer <developer@lists.illumos.org>
Subject: Re: [developer] [REVIEW] 16763: dladm simnet functionality should be documented
Date: Wed, 11 Sep 2024 20:48:59 +0200	[thread overview]
Message-ID: <22C789E4-5811-43E0-A48D-B361F75A7CF0@eenfach.de> (raw)
In-Reply-To: <ba6c5d9b62dc35bbec7fe9257e27f936@welliver.org>

Dear William,

maybe the create-simnet subcommand should include a very brief explanation what “simnet” actually is. So that end users understand that it is mostly a debugging facility.

Regards,

Olaf Bohlen
olbohlen@eenfach.de

> Am 11.09.2024 um 07:24 schrieb william@welliver.org:
> 
> Hello all,
> 
> I have an initial contribution for basic simnet documentation that I'd like to have reviewed.
> 
> Gerrit Review: https://code.illumos.org/c/illumos-gate/+/3683
> 
> Bug Ticket: https://www.illumos.org/issues/16763
> 
> For ease of review, I attached an HTML rendition of the proposed man page changes. Unfortunately, redmine helpfully renders the markup to text. I've temporarily made the page available at:
> 
> http://bill.welliver.org/dist/dladm.8.html
> 
> Any feedback would be welcome!
> 
> Best,
> 
> Bill
> 
> ------------------------------------------
> illumos: illumos-developer
> Permalink: https://illumos.topicbox.com/groups/developer/Ta3283bbd32ecf85f-M32dbe25c3985f34d45a63077
> Delivery options: https://illumos.topicbox.com/groups/developer/subscription


  reply	other threads:[~2024-09-11 18:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-11  5:24 william
2024-09-11 18:48 ` Olaf Bohlen [this message]
2024-09-12  4:20   ` [developer] " H. William Welliver
2024-09-12  8:33     ` Olaf Bohlen
2024-09-12  8:46       ` Joshua M. Clulow
2024-09-27 21:21 william

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=22C789E4-5811-43E0-A48D-B361F75A7CF0@eenfach.de \
    --to=olbohlen@eenfach.de \
    --cc=developer@lists.illumos.org \
    /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).