[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Add a tentative .clang-format for LilyPond. (issue 561340043 by addr
|
From: |
Carl . D . Sorensen |
|
Subject: |
Re: Add a tentative .clang-format for LilyPond. (issue 561340043 by address@hidden) |
|
Date: |
Fri, 31 Jan 2020 10:33:38 -0800 |
IIUC, this is a .clang-format that can be (but is not required to be)
used to format source code and prevent comments about formatting.
At this point, we are not enforcing a shift to clang-format as the code
standard for LilyPond.
If this is true, LGTM.
If we are enforcing a shift to clang-format, then I think we need an
LGTM from David K.
https://codereview.appspot.com/561340043/
- Add a tentative .clang-format for LilyPond. (issue 561340043 by address@hidden), lemzwerg, 2020/01/27
- Re: Add a tentative .clang-format for LilyPond. (issue 561340043 by address@hidden), hanwenn, 2020/01/29
- Re: Add a tentative .clang-format for LilyPond. (issue 561340043 by address@hidden), lemzwerg, 2020/01/29
- Re: Add a tentative .clang-format for LilyPond. (issue 561340043 by address@hidden), nine . fierce . ballads, 2020/01/29
- Re: Add a tentative .clang-format for LilyPond. (issue 561340043 by address@hidden), hanwenn, 2020/01/31
- Re: Add a tentative .clang-format for LilyPond. (issue 561340043 by address@hidden), nine . fierce . ballads, 2020/01/31
- Re: Add a tentative .clang-format for LilyPond. (issue 561340043 by address@hidden), hanwenn, 2020/01/31
- Re: Add a tentative .clang-format for LilyPond. (issue 561340043 by address@hidden),
Carl . D . Sorensen <=
- Re: Add a tentative .clang-format for LilyPond. (issue 561340043 by address@hidden), hanwenn, 2020/01/31
- Re: Add a tentative .clang-format for LilyPond. (issue 561340043 by address@hidden), Carl . D . Sorensen, 2020/01/31