From: Dietmar Maurer <dietmar@proxmox.com>
To: Roland Kammerer <roland.kammerer@linbit.com>, drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] drbdmanage package name
Date: Mon, 11 May 2015 10:43:38 +0200 (CEST) [thread overview]
Message-ID: <1348675331.157.1431333818922.JavaMail.open-xchange@ronja.mits.lan> (raw)
In-Reply-To: <20150511074859.GU1968@rck.sh>
> Currently, it is a "frankenstein-package" anyways, because it contains
> the server, the modules which could be used for example to write your
> own client, and the client itself...
>
> I will keep it in mind and think about renaming/splitting.
Yes, I guess you should split the package if it contains a library.
But the package with the binary toolkit should be called 'drbdmanage',
an sections should be 'admin' instead of 'python'.
I also noticed that you do not apply the quilt patches, which is good because
the included patches are out of date. I suggest to remove patch
0001-var-lib-drbdd.patch from debian/patches/series to avoid confusion.
prev parent reply other threads:[~2015-05-11 8:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 6:44 [Drbd-dev] drbdmanage package name Dietmar Maurer
2015-05-11 7:49 ` Roland Kammerer
2015-05-11 8:43 ` 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=1348675331.157.1431333818922.JavaMail.open-xchange@ronja.mits.lan \
--to=dietmar@proxmox.com \
--cc=drbd-dev@lists.linbit.com \
--cc=roland.kammerer@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