From: Philipp Reisner <philipp.reisner@linbit.com>
To: YAMAGUCHI Masashi <yamagu-m@saturn.dti.ne.jp>
Cc: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] [PATCH] scripts/notify.sh: Fix event identification
Date: Fri, 28 May 2010 11:13:10 +0200 [thread overview]
Message-ID: <201005281113.10709.philipp.reisner@linbit.com> (raw)
In-Reply-To: <201005272346.o4RNkutF012753@smtp14.dti.ne.jp>
Am Freitag, 28. Mai 2010, um 01:46:56 schrieb YAMAGUCHI Masashi:
> Hi,
>
> "notify.sh" cannot identify the events of "notify-pri-lost.sh" and
> "notify-pri-lost-after-sb.sh" so the mails sent by these scripts are
> treated as "Unspecified DRBD notification".
>
Thanks for pointing that out, patch goes in.
Best,
Phil
--
: Dipl-Ing Philipp Reisner
: LINBIT | Your Way to High Availability
: Tel: +43-1-8178292-50, Fax: +43-1-8178292-82
: http://www.linbit.com
DRBD(R) and LINBIT(R) are registered trademarks of LINBIT, Austria.
prev parent reply other threads:[~2010-05-28 9:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 23:46 [Drbd-dev] [PATCH] scripts/notify.sh: Fix event identification YAMAGUCHI Masashi
2010-05-28 9:13 ` Philipp Reisner [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=201005281113.10709.philipp.reisner@linbit.com \
--to=philipp.reisner@linbit.com \
--cc=drbd-dev@lists.linbit.com \
--cc=yamagu-m@saturn.dti.ne.jp \
/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