https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-6131 Lustre <p>I have found several bad commit ids listed in Lustre-commit: fields in commit messages.</p> <p>Since these are all because we are back-porting commits, the IDs should already exist in the main repository. So perhaps we can get HPDD Checkpatch to validate the commit IDs?</p> LU-6131

Detect bad commit ids in Lustre-commit: field

Task Minor Resolved Won't Fix Andreas Dilger Christopher Morrone Fri, 16 Jan 2015 23:06:34 +0000 Thu, 2 Dec 2021 21:24:11 +0000 Thu, 2 Dec 2021 21:24:11 +0000 0 6 <p>Chris, this seems reasonable, and should be doable by the script. Do you have specific examples where the commit hash was bad? Presumably they are all on b2_5? In some cases I guess there are commit hashes from the upstream kernel in commit messages going to master, but they should be marked with <tt>Linux-commit:</tt>. </p> <p>Here are a couple:</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>5748379d28846c672f793ba1f8e143e63531dd05 e5966bdbb7c7644cc04580ad6b4a9006def3f758 </pre> </div></div> <p>While it would be possible to warn on a bad commit ID, I don't think it is possible to make this an error, because backporting patches with these commit messages to repositories that don't have the original commit should not fail.</p> Development End date Tue, 20 Jan 2015 23:06:34 +0000 Rank 1|hzx45z: Rank (Obsolete) 17085 Start date Fri, 16 Jan 2015 23:06:34 +0000