From c2bdbdcb475b537488b3213a8929d8bd17614877 Mon Sep 17 00:00:00 2001 From: Patrick Vogler Date: Tue, 20 Jun 2023 14:35:55 +0000 Subject: [PATCH] Update 'Coding Style' --- Coding-Style.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Coding-Style.md b/Coding-Style.md index c0b3804..5d1e611 100644 --- a/Coding-Style.md +++ b/Coding-Style.md @@ -29,11 +29,11 @@ This document discusses practices and style for programmers working on the BigWh Above all, the following rule from the GNOME developer documentation should always be followed. >The single most important rule when writing code is this: check the surrounding code and try to imitate it. > ->As a maintainer it is dismaying to receive a patch that is obviously in a different coding style to the surrounding code. This is >disrespectful, like someone tromping into a spotlessly-clean house with muddy shoes. +>As a maintainer it is dismaying to receive a patch that is obviously in a different coding style to the surrounding code. This is disrespectful, like someone tromping into a spotlessly-clean house with muddy shoes. > ->So, whatever this document recommends, if there is already written code and you are contributing to it, keep its current style >consistent even if it is not your favorite style. +>So, whatever this document recommends, if there is already written code and you are contributing to it, keep its current style consistent even if it is not your favorite style. > ->Most importantly, do not make your first contribution to a project a change in the coding style to suit your taste. That is >incredibly disrespectful. +>Most importantly, do not make your first contribution to a project a change in the coding style to suit your taste. That is incredibly disrespectful. ## Formatting ### Indentation