| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Rename HACKING.md to the more standard CODING_STYLE.md | Robert Ancell | 2022-11-15 | 1 | -0/+0 |
| | | |||||
| * | Rewrite the contribution guidelines. | Robert Ancell | 2022-11-13 | 1 | -22/+92 |
| | | | | | In particular set the expectation for reviews and document when MRs will be closed due to inactivity. | ||||
| * | Split code of conduct into separate document | Robert Ancell | 2022-11-13 | 2 | -185/+184 |
| | | |||||
| * | Fix broken link to communication guidelines, by fixing the name of this section | Robert Ancell | 2022-11-10 | 1 | -1/+1 |
| | | |||||
| * | Switch to 'main' everywhere | Georges Basile Stavracas Neto | 2022-04-26 | 2 | -3/+3 |
| | | |||||
| * | docs: Fix markdown formatting | Georges Basile Stavracas Neto | 2019-07-22 | 1 | -2/+2 |
| | | |||||
| * | docs: Document the Communication Guidelines | Georges Basile Stavracas Neto | 2019-04-02 | 1 | -1/+138 |
| | | | | | | | | | | These are the documented guidelines for when communicating and interacting with humans. Not following the documented guidelines means the comment will be removed, or the ticket will be closed. [skip ci] | ||||
| * | project: Document maintainers and workflow | Georges Basile Stavracas Neto | 2018-07-16 | 2 | -5/+71 |
| | | | | | | | | | | | | | | It is important that potential contributors know who they should get in touch, who is supposed to review their work, and maintainers to know how they should introduce changes. Thus, this commit documents the current maintainers together with what they maintain, and the workflow between maintainers as well. [skip ci] | ||||
| * | docs: Remove trailing space from code example | Georges Basile Stavracas Neto | 2018-06-19 | 1 | -1/+1 |
| | | |||||
| * | docs: Document more of the code style | Georges Basile Stavracas Neto | 2018-06-19 | 1 | -0/+36 |
| | | |||||
| * | docs: Improve code style guideline | Georges Basile Stavracas Neto | 2018-05-29 | 1 | -0/+42 |
| | | |||||
| * | docs: Fix code block | Georges Basile Stavracas Neto | 2018-05-13 | 1 | -0/+1 |
| | | |||||
| * | docs: Document style of comments | Georges Basile Stavracas Neto | 2018-05-12 | 1 | -0/+12 |
| | | |||||
| * | project: Add coding style and contribution guidelines | Georges Basile Stavracas Neto | 2018-05-02 | 2 | -0/+271 |
| | | | | | And also update the README file. | ||||
| * | Remove API reference, as it's incomplete and going away for next cycle | Rodrigo Moya | 2011-04-01 | 6 | -187/+0 |
| | | |||||
| * | configure: Group pkg-config checks based on how they are used | Thomas Wood | 2011-02-19 | 1 | -2/+2 |
| | | | | | | | | Group the pkg-config checks so that pkg-config can remove duplicated CFLAGS and LIBS. https://bugzilla.gnome.org/show_bug.cgi?id=636593 | ||||
| * | Fix various issues raised by running distcheck | Thomas Wood | 2010-05-21 | 1 | -1/+1 |
| | | |||||
| * | Add libgnome-control-center with two new classes: CcShell and CcPanel | Thomas Wood | 2010-05-18 | 6 | -0/+187 |
| CcShell is an abstract class that represents an instance of a control center shell. It provides access to some of the properties of the shell that panels will need to read or change. When a panel is created it has an instance of CcShell available that represents the current shell. CcPanel is an abstract class used to implement panels for the shell. A panel contains a collection of related settings that are displayed within the shell window. | |||||
 |
index : delta/gnome/gnome-control-center.git | |
| gitlab.gnome.org: GNOME/gnome-control-center.git |
| summaryrefslogtreecommitdiff |