[LUDOC-426] LBUG vs. LBug - Acronym or Abbreviation? Created: 24/Dec/18  Updated: 08/Nov/19  Resolved: 08/Nov/19

Status: Resolved
Project: Lustre Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Trivial
Reporter: Brett Lee (Inactive) Assignee: Lustre Manual Triage
Resolution: Won't Fix Votes: 0
Labels: easy

Severity: 4
Rank (Obsolete): 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.



 Comments   
Comment by Andreas Dilger [ 08/Nov/19 ]

All of the documentation uses LBUG() and this is what is printed on the console. I don't see any benefit in changing this.

Generated at Sat Feb 10 03:42:50 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.