On 2016-09-01 at 21:10 "'Christopher Koch' via Akaros" <[email protected]> wrote: > The style guide Akaros has chosen to follow is slightly different from many > of the common ones (kernel, llvm, ...) and setting up tools to automate the > formatting doesn't quite do it right.
The intent is to be like Linux's format. If you have code that is formatted in accordance with the Linux kernel, then that is fine. If I, or some tool, complains about code that is OK by Linux's standards, let me know or ignore that tool. The only major deviation we have is 4-space vs 8-space indents. I regret that choice, but I am also reluctant to do a blanket change because I value the results of git blame. Last I checked, blame did not have an option to ignore a commit. That being said, the comments I regularly make about tools not being perfect when it comes to code formatting are also true for the Linux style. I forget where I saw that same point on LKML or wherever. > It seems I can either choose to (a) format manually, (b) use one out of a > number of broken/unconfigurable tools, (c) spend hours or days fixing the > broken tools or adding configuration options. It seems that all three of > these are a huge waste of time. (And a huge source of frustration.) Honestly, I do option 'a' (manual format), in that I write to that particular style from the get-go. > You should especially take this into consideration given the developer > velocity points that have been brought up over the last few months. I wonder how much time is spent on formatting versus the endless discussions about formatting. Barret -- You received this message because you are subscribed to the Google Groups "Akaros" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
