Page History
...
No Format |
---|
ln -sf ../../build/commit-msg .git/hooks/ ln -sf ../../build/prepare-commit-msg .git/hooks/ |
At git commit}
time this will run the {{build/prepare-commit-msg
script from the currently Lustre tree to check the code changes for style errors using build/checkpatch.pl
, and add comments at the bottom end of the commit message with any warnings or errors. After the commit message has been saved, the build/commit-msg
script will verify that the commit message format matches the format specified above, and insert the Commit-Id:
field into the commit message, if one isn't already present.
...
No Format |
---|
Acked-by: User Name <user@domain.com> Tested-by: User Name <user@domain.com> Reported-by: User Name <user@domain.com> Reviewed-by: User Name <user@domain.com> CC: User Name <user@domain.com> {Organization}-bug-id: arbitrary bug tracking identifier OriginalLustre-commit: {git commit hash of original patch} Lustre-change: {Gerrit change URL of original patch} Test-Parameters: additional testing parameters |
The {Organization}-bug-id:
tag (e.g. WhamcloudIntel-bug-id: ORI-123
, Xyratex-bug-id: MRP-123
, or Oracle-bug-id: b=12345
) can be used to track this patch in other bug databases.
OriginalLustre-commit:
is and Lustre-change:
are used to reference the original version of a patch that is being ported to another branch or to the upstream kernel.
Test-Parameters:
is used to specify additional testing parameters for this patch, see Changing Test Parameters with Gerrit Commit Messages.
...