From: Dietmar Maurer <dietmar@proxmox.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] cluster initialization with drbdmanage
Date: Wed, 20 May 2015 17:02:22 +0200 (CEST) [thread overview]
Message-ID: <1711309736.185.1432134142832.JavaMail.open-xchange@ronja.mits.lan> (raw)
In-Reply-To: <20150520132305.GY1968@rck.sh>
> It is the third time I ask you to switch to drbd-user and to not TO/CC
> me. Is it really that difficult?
Yes, it is difficult because:
1.) I consider it bad behavior to switch an existing thread
from one list to another. The archives gets inconsistent that way.
2.) It is unclear what you mean by 'such questions'. For me all this
are development related issues (bugs, missing features, ...).
3.) My environment adds your email address automatically if I press reply.
As requested, I will post further replies to drbd-user.
prev parent reply other threads:[~2015-05-20 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 9:26 [Drbd-dev] cluster initialization with drbdmanage Dietmar Maurer
2015-05-20 11:55 ` Roland Kammerer
2015-05-20 12:09 ` Dietmar Maurer
2015-05-20 12:40 ` Roland Kammerer
2015-05-20 12:54 ` Dietmar Maurer
2015-05-20 13:23 ` Roland Kammerer
2015-05-20 15:02 ` Dietmar Maurer [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=1711309736.185.1432134142832.JavaMail.open-xchange@ronja.mits.lan \
--to=dietmar@proxmox.com \
--cc=drbd-dev@lists.linbit.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