Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | man: document preference for secure_getenv() in coding style | Lennart Poettering | 2024-10-14 | 1 | -0/+8 |
| | |||||
* | docs/CODING_STYLE: document that we nowadays prefer (const char*) for func ↵ | Mike Yuan | 2024-07-02 | 1 | -1/+13 |
| | | | | | | ret type Addresses https://github.com/systemd/systemd/pull/33567#discussion_r1662818225 | ||||
* | CODING_STYLE: document "reterr_" return parameters | Lennart Poettering | 2024-06-13 | 1 | -14/+48 |
| | | | | | | | In some recent PRs (e.g. #32628) I started to systematically name return parameters that shall only be initialized on failure (because they carry additional error meta information, such as the line/column number of parse failures or so). Let's make this official in the coding style. | ||||
* | Merge pull request #31648 from neighbourhoodie/review-content | Zbigniew Jędrzejewski-Szmek | 2024-04-17 | 1 | -1/+1 |
|\ | | | | | | | I did the merge manually to resolve a trivial conflict. | ||||
| * | docs/CODING_STYLE: remove whitespace | hulkoba | 2024-03-27 | 1 | -1/+1 |
| | | |||||
* | | docs: Add Tests section to coding style doc | Daan De Meyer | 2024-04-10 | 1 | -0/+10 |
|/ | |||||
* | docs/CODING_STYLE: fix typo (CLONE_VORK -> VFORK) | Mike Yuan | 2024-02-24 | 1 | -1/+1 |
| | |||||
* | Revert "docs: use collections to structure the data" | Zbigniew Jędrzejewski-Szmek | 2024-02-23 | 1 | -0/+782 |
| | | | | | | | | | This reverts commit 5e8ff010a1436d33bbf3c108335af6e0b4ff7a2a. This broke all the URLs, we can't have that. (And actually, we probably don't _want_ to make the change either. It's nicer to have all the pages in one directory, so one doesn't have to figure out to which collection the page belongs.) | ||||
* | docs: use collections to structure the data | hulkoba | 2024-02-22 | 1 | -782/+0 |
| | |||||
* | doc: readd vanished ``` | Lennart Poettering | 2023-10-11 | 1 | -0/+1 |
| | | | | | This disappeared in 1e8f5f79e1b6ae2b4115df280c626b71c54a5bb6, let's restore it. | ||||
* | docs: fix typo | Yu Watanabe | 2023-08-01 | 1 | -1/+1 |
| | |||||
* | tree-wide: "<n>bit" → "<n>-bit" | Zbigniew Jędrzejewski-Szmek | 2023-07-02 | 1 | -1/+1 |
| | | | | In some places, "<n> bits" is used when more appropriate. | ||||
* | docs: document threading situation in coding style | Lennart Poettering | 2023-06-23 | 1 | -0/+29 |
| | |||||
* | doc: say in CODING_STYLE that AT_EMPTY_PATH should be implied on openat() ↵ | Lennart Poettering | 2023-04-25 | 1 | -0/+9 |
| | | | | | | | | style APIs (and NULL path is OK) As discussed here: https://github.com/systemd/systemd/pull/27397#issuecomment-1521630044 | ||||
* | CODING_STYLE: note that 'unsigned' form is preferred over 'unsigned int' | Dmitry V. Levin | 2023-03-08 | 1 | -1/+1 |
| | |||||
* | docs/CODING_STYLE: add sentence about redirection operators | Zbigniew Jędrzejewski-Szmek | 2023-02-06 | 1 | -2/+5 |
| | |||||
* | docs, man: consistently use comma after "For example" | Dmitry V. Levin | 2023-01-23 | 1 | -1/+1 |
| | |||||
* | docs: fix grammar a bit | Dmitry V. Levin | 2023-01-23 | 1 | -2/+2 |
| | |||||
* | docs: fix a few typos | Dmitry V. Levin | 2023-01-23 | 1 | -1/+1 |
| | |||||
* | doc: document how we expect empty lines to be used | Lennart Poettering | 2023-01-17 | 1 | -2/+16 |
| | |||||
* | CODING_STYLE: fix 'better' typo | Sam James | 2023-01-06 | 1 | -1/+1 |
| | |||||
* | CODING_STYLE: fix header level | Lennart Poettering | 2022-09-08 | 1 | -1/+1 |
| | |||||
* | docs: Some CODING_STYLE additions | Lennart Poettering | 2022-09-07 | 1 | -0/+38 |
| | |||||
* | docs: suggests people use path_extract_filename() + path_extract_directory() | Lennart Poettering | 2022-08-23 | 1 | -5/+5 |
| | |||||
* | tree-wide: fix typo | Yu Watanabe | 2022-06-10 | 1 | -1/+1 |
| | |||||
* | CODING_STYLE: say that inet_ntop() is a no no | Zbigniew Jędrzejewski-Szmek | 2022-06-06 | 1 | -0/+5 |
| | |||||
* | docs: document how we usually define enums | Lennart Poettering | 2022-03-14 | 1 | -0/+40 |
| | |||||
* | docs: document we use C11 with GNU extensions now | Lennart Poettering | 2022-03-14 | 1 | -1/+15 |
| | | | | Follow-up for: #22711 | ||||
* | Update CODING_STYLE.md | bearhoney | 2022-02-07 | 1 | -1/+1 |
| | | | Fixed typo. | ||||
* | docs: fix typos and improve language | Erik Sjölund | 2022-01-26 | 1 | -1/+1 |
| | | | | | Fix typos and improve the language by adding a few commas and a missing word. | ||||
* | docs: mention RET_NERRNO() in CODING_STYLE.md | Lennart Poettering | 2021-11-16 | 1 | -0/+19 |
| | |||||
* | Change gendered terms to be gender-neutral (#21325) | Emily Gonyer | 2021-11-12 | 1 | -1/+1 |
| | | | Some typos are also fixed. | ||||
* | CODING_STYLE: allow joined variable declarations and function calls | Zbigniew Jędrzejewski-Szmek | 2021-11-03 | 1 | -9/+18 |
| | | | | | | | | | … but only for a single variable. The guidelines already allowed declaring variables at the point of initialization. But not making a function call to do that. Let's allow that now. The existing style of declaring and initializing seperate is still allowed, and whatever makes most sense should be used. | ||||
* | doc: document that alloca_safe() and friends are the APIs to use | Lennart Poettering | 2021-10-14 | 1 | -11/+19 |
| | |||||
* | docs: add spdx tags to all .md files | Zbigniew Jędrzejewski-Szmek | 2021-09-27 | 1 | -0/+1 |
| | | | | | | I have no idea if this is going to cause rendering problems, and it is fairly hard to check. So let's just merge this, and if it github markdown processor doesn't like it, revert. | ||||
* | docs: add coding style example | Anders Wenhaug | 2021-06-24 | 1 | -0/+8 |
| | | | | Add example of how to structure else-blocks following a multiline block. | ||||
* | docs: update coding style a bit | Zbigniew Jędrzejewski-Szmek | 2021-06-11 | 1 | -13/+20 |
| | | | | | | | | | Say that r should be declared at the top of the function. Don't say that fixed buffers result in truncation, right after saying that they must only be used if size is known. Adjust order of examples to be consistent. | ||||
* | docs/CODING_STYLE: fix some typos | Štěpán Němec | 2021-06-10 | 1 | -4/+4 |
| | |||||
* | docs: add ARCHITECTURE.md with code map | Luca Boccassi | 2021-06-03 | 1 | -25/+0 |
| | | | | | Initial and coarse version of a code map, useful for people getting started and looking at the repository for the first time. | ||||
* | docs: more markup | Zbigniew Jędrzejewski-Szmek | 2021-03-11 | 1 | -5/+5 |
| | |||||
* | docs: document not to use FILENAME_MAX in our codebase | Lennart Poettering | 2021-03-08 | 1 | -0/+6 |
| | | | | It's a weird thing. Let's explain why. | ||||
* | docs: update coding style for `return (void) func(...)` | Anita Zhang | 2020-10-27 | 1 | -0/+8 |
| | | | | | Seems that people think it's useful for brevity so make it explicit in the CODING_STYLE. | ||||
* | docs: some coding style updates | Lennart Poettering | 2020-10-19 | 1 | -8/+33 |
| | | | | | | | | | | Primarily: 1. Mention that we prefer if return parameters carry "ret_" as prefix in their name 2. Clarify that debug-level logging is always OK, and irrelevant to when deciding whether a function is logging or non-logging. | ||||
* | coding style: document how to break a function declaration | Luca Boccassi | 2020-08-20 | 1 | -0/+11 |
| | |||||
* | docs: spelling fixes | Joerg Behrmann | 2020-08-04 | 1 | -2/+2 |
| | |||||
* | fix typo | Tomer Shechner | 2020-07-07 | 1 | -1/+1 |
| | | | | | I was thoroughly reading your nice coding style page and found out that you guys missed an 's'. 😁 | ||||
* | tree-wide: use "hostname" spelling everywhere | Zbigniew Jędrzejewski-Szmek | 2020-04-21 | 1 | -1/+1 |
| | | | | | | | | It's not that I think that "hostname" is vastly superior to "host name". Quite the opposite — the difference is small, and in some context the two-word version does fit better. But in the tree, there are ~200 occurrences of the first, and >1600 of the other, and consistent spelling is more important than any particular spelling choice. | ||||
* | docs: make sure there's only one # markdown header in each file | Lennart Poettering | 2019-12-13 | 1 | -1/+1 |
| | | | | | | | @bertob wants us to be strict here, and only have one "#" header per markdown file, and use "##" (or "###", …) for all others. Interestingly, we mostly got this right already, but this fixes a few cases where this wasn't correct. | ||||
* | docs: make it pretty | Tobias Bernard | 2019-12-11 | 1 | -0/+1 |
| | | | | | | | Add custom Jekyll theme, logo, webfont and .gitignore FIXME: the markdown files have some H1 headers which need to be replaced with H2 | ||||
* | docs: place all our markdown docs in rough categories | Lennart Poettering | 2019-12-11 | 1 | -0/+1 |
| |