From: Dave Wysochanski <dwysocha@redhat.com>
To: lvm-devel@redhat.com
Subject: Deprecating LVM code / commands?
Date: Mon, 16 Feb 2009 12:26:54 -0500 [thread overview]
Message-ID: <1234805214.2574.29.camel@f10-node1> (raw)
I know everyone is focused on features in the next RHEL6 / Fedora, but
have we thought enough about what we could deprecate? With a major
release around the corner, we don't get this opportunity very often.
For example, do we really need to keep pool and lvm1 formats for the
next 7 years? If not, we could more easily clean up some of the
internal abstractions. Other code we could remove that would make
future features / maintenance easier?
Or any LVM commands that should be removed completely?
Note that there is at least 2 approaches:
1) Remove the code completely
2) Deprecate but don't remove
next reply other threads:[~2009-02-16 17:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 17:26 Dave Wysochanski [this message]
2009-02-17 19:40 ` Deprecating LVM code / commands? Alasdair G Kergon
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=1234805214.2574.29.camel@f10-node1 \
--to=dwysocha@redhat.com \
--cc=lvm-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.