Lines Matching +full:format +full:- +full:c

4 <!---
5 Please use a pull request to the appropriate branch ('stable' for backward-compatible bug fixes for…
6 -->
7 …e your commits well-organized and [atomic](https://en.wikipedia.org/wiki/Atomic_commit#Atomic_comm…
8 Check that tests (including "examples") pass using `make prove-all`.
12 …efficiency of reviewing and facilitates use of [`git bisect`](https://git-scm.com/docs/git-bisect).
15 It is useful to create a WIP (work in progress) pull request for any long-running development so th…
20 …-by: Helpful User <helpful@example.com>` or [`Co-authored-by: Snippet Mentor <code.by@comment.com>…
22 If your author information or email becomes inconsistent (look at `git shortlog -se`), please edit …
24 … and support it, their names are included in the automatically generated user-manual documentation.
31 You can use `make format` to help conform to coding conventions of the project, but try to avoid mi…
43 (c) The contribution was provided directly to me by some other person who certified (a), (b) or (c)…
45 …tion (including all personal information I submit with it, including my sign-off) is maintained in…
50 …ntributors receive appropriate recognition through informal and academically-recognized credit sys…
58 Authors of publications about libCEED as a whole, including DOI-bearing archives, shall offer co-au…
59 … libCEED contributions shall evaluate those listed in `AUTHORS` and offer co-authorship to those w…
61 …-authorship expectation for those publishing about use of libCEED (versus creation of new features…