From: Christophe Varoqui <christophe.varoqui@gmail.com>
To: aruna <aruna@linux.vnet.ibm.com>
Cc: dm-devel@redhat.com
Subject: Re: [PATCH] [multipath-tools]'multipath' with -h and -t option, it returns '1' (fail) for successful command execution.
Date: Tue, 04 Oct 2011 19:52:15 +0200 [thread overview]
Message-ID: <1317750735.6857.2.camel@lapoo.opensvc.com> (raw)
In-Reply-To: <1317706703.1886.132.camel@arunaltc>
On mar., 2011-10-04 at 11:08 +0530, aruna wrote:
> Hi,
>
> The patch handles the exit status of -h and -t option for multipath
> command.
>
You patch does not apply to the HEAD. And you should submit with patch
inline for "git am" to work and preserve your patch comment and
authorship.
Thanks,
cvaroqui
> # multipath -h
> multipath-tools v0.4.9 (05/33, 2016)
> Usage:
> multipath [-d] [-r] [-v lvl] [-p pol] [-b fil] [dev]
> multipath -l|-ll|-f [-v lvl] [-b fil] [dev]
> multipath -F [-v lvl]
> multipath -t
> multipath -h
>
> .......
>
> # echo $?
> 1
>
>
> # multipath -t | more
> defaults {
> verbosity 2
> polling_interval 10
> udev_dir "/dev"
> multipath_dir "/lib64/multipath"
> ...
> }
> ...
>
>
> # echo $?
> 1
>
>
> Since kernel.org is unavailable i have got the recent snapshot from
>
> http://git.opensvc.com/?p=multipath-tools/.git;a=snapshot;h=f7735ad547d9ebb952993ac0a6def0400fb23c80;sf=tgz
>
>
> Thanks,
> Aruna Balakrishnaiah
>
next parent reply other threads:[~2011-10-04 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1317706703.1886.132.camel@arunaltc>
2011-10-04 17:52 ` Christophe Varoqui [this message]
[not found] <20111005143410.4265.68055.stgit@arunaltc>
2011-10-05 20:45 ` [PATCH][multipath-tools]'multipath' with -h and -t option, it returns '1' (fail) for successful command execution Christophe Varoqui
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=1317750735.6857.2.camel@lapoo.opensvc.com \
--to=christophe.varoqui@gmail.com \
--cc=aruna@linux.vnet.ibm.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@redhat.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 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.