All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@trained-monkey.org>
To: Lukasz Florczak <lukasz.florczak@linux.intel.com>,
	linux-raid@vger.kernel.org
Cc: colyli@suse.de, pmenzel@molgen.mpg.de
Subject: Re: [PATCH 1/4] mdadm: Respect config file location in man
Date: Mon, 4 Apr 2022 21:12:40 -0400	[thread overview]
Message-ID: <1b383112-0d59-657e-2e99-9da3a915d8ac@trained-monkey.org> (raw)
In-Reply-To: <20220318082607.675665-2-lukasz.florczak@linux.intel.com>

On 3/18/22 04:26, Lukasz Florczak wrote:
> Default config file location could differ depending on OS (e.g. Debian family).
> This patch takes default config file into consideration when creating mdadm.man
> file as well as mdadm.conf.man.
> 
> Rename mdadm.conf.5 to mdadm.conf.5.in. Now mdadm.conf.5 is generated automatically.
> 
> Signed-off-by: Lukasz Florczak <lukasz.florczak@linux.intel.com>
> ---


Applied!

Thanks,
Jes



  parent reply	other threads:[~2022-04-05  2:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18  8:26 [PATCH v2 0/4] Manual improvements Lukasz Florczak
2022-03-18  8:26 ` [PATCH 1/4] mdadm: Respect config file location in man Lukasz Florczak
2022-03-20  9:54   ` Coly Li
2022-03-21  8:14     ` Mariusz Tkaczyk
2022-03-21 14:54       ` Coly Li
2022-03-21 15:06         ` Coly Li
2022-03-22  7:39         ` Mariusz Tkaczyk
2022-04-05  1:12   ` Jes Sorensen [this message]
2022-03-18  8:26 ` [PATCH 2/4] mdadm: Update ReadMe Lukasz Florczak
2022-03-20 14:05   ` Coly Li
2022-04-05  1:15   ` Jes Sorensen
2022-03-18  8:26 ` [PATCH 3/4] mdadm: Update config man regarding default files and multi-keyword behavior Lukasz Florczak
2022-03-20 14:54   ` Coly Li
2022-04-05  1:15   ` Jes Sorensen
2022-03-18  8:26 ` [PATCH 4/4] mdadm: Update config manual Lukasz Florczak
2022-03-20 14:54   ` Coly Li
2022-04-05  1:15   ` Jes Sorensen

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=1b383112-0d59-657e-2e99-9da3a915d8ac@trained-monkey.org \
    --to=jes@trained-monkey.org \
    --cc=colyli@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=lukasz.florczak@linux.intel.com \
    --cc=pmenzel@molgen.mpg.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.