Details
-
Bug
-
Resolution: Won't Fix
-
Trivial
-
None
-
None
-
4
-
9223372036854775807
Description
Hello. Much as LUDOC-324 updated the Lustre manual to ensure that LNet is used with consistent case in general documentation, I'm thinking that the same might apply to the term LBug. For example, in situations where the LBug term is used as a macro, it should remain upper case (LBUG), and when it is used in a parameter (panic_on_lbug) it should remain lower case. In general, though, it seems it might be better as LBug, as it is not an acronym, AFAIK.
All of the documentation uses LBUG() and this is what is printed on the console. I don't see any benefit in changing this.