linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jes.sorensen@gmail.com
To: Zhilong Liu <zlliu@suse.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH] mdadm:add man page for --symlinks
Date: Mon, 06 Mar 2017 16:34:57 -0500	[thread overview]
Message-ID: <wrfjr32aks1q.fsf@gmail.com> (raw)
In-Reply-To: <1488767997-21594-1-git-send-email-zlliu@suse.com> (Zhilong Liu's message of "Mon, 6 Mar 2017 10:39:57 +0800")

Zhilong Liu <zlliu@suse.com> writes:
> In build and create mode:
> --symlinks
> 	Auto creation of symlinks in /dev to /dev/md, option --symlinks
> 	must be 'no' or 'yes' and work with --create and --build.
> In assemble mode:
> --symlinks
> 	See this option under Create and Build options.
>
> Signed-off-by: Zhilong Liu <zlliu@suse.com>

Applied!

Thanks,
Jes

      reply	other threads:[~2017-03-06 21:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06  2:39 [PATCH] mdadm:add man page for --symlinks Zhilong Liu
2017-03-06 21:34 ` jes.sorensen [this message]

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=wrfjr32aks1q.fsf@gmail.com \
    --to=jes.sorensen@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=zlliu@suse.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).