Page History

...

The first line of the comment is the subject or summary of the change, and should include the Lustra Jira ID at the beginning of the line. A Lustre Jira ticket is one that begins with LU and is therefore part of the Lustre project within Jira. If the patch is submitted for the fs/lustre-release repository without a Lustre Jira ID in the first line, then it will automatically receive a -2 review which will prevent the patch from being submitted to a release branch. The component: field is the Lustre subsystem that the commit is related to, for example llite, lov, ldlm, socklnd, lnet, etc.

Please make sure the Change-Id: line are on the bottom of the comment. This is also both required (as is the Signed-off-by line) by the fs/lustre-release project (at least) in order for the patch to be approved.  If your comments are excluding the Change-Id the patch will be rejected at submission time. The Change-Id field should be added using the commit-msg hook, see below.

...