From: Christopher J. Morrone <morrone2@llnl.gov>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] Lustre versioning overhaul, input requested
Date: Tue, 16 Feb 2016 17:55:52 -0800 [thread overview]
Message-ID: <56C3D328.8080202@llnl.gov> (raw)
Hello everyone,
I am hoping to make a number of build and rpm packaging improvements
early in the Lustre 2.9 development cycle. One of the early changes, on
which a number of later changes currently depend, is an overhaul of the
method used to version Lustre.
I would love to get some more eyes on this change and get any critiques
in soon so we can get this landed potentially a week or two from now.
You can find the main jira ticket for the lustre versioning overhaul here:
https://jira.hpdd.intel.com/browse/LU-7699
The last comment in the ticket points to the current three patches
involved in the overhaul. The first patch is the most significant of
the three in size and scope:
http://review.whamcloud.com/18107
Change 18107 has a fairly lengthy commit comment describing the changes.
Also take a look at the file "Documentation/versioning.txt" inside of
change 18107 to see a description of how versioning works under the new
system.
Any feedback is welcome! A lack of feedback will be interpreted as
acceptance. :)
Chris
reply other threads:[~2016-02-17 1:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=56C3D328.8080202@llnl.gov \
--to=morrone2@llnl.gov \
--cc=lustre-devel@lists.lustre.org \
/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.