From 8f76be93c425cfc36c4b6f58fc126b5ca1dbee62 Mon Sep 17 00:00:00 2001 From: JozanLeClerc Date: Sun, 1 Nov 2020 18:13:40 +0100 Subject: Typo --- org/dergods_style_v0.1.org | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'org') diff --git a/org/dergods_style_v0.1.org b/org/dergods_style_v0.1.org index 7637f8f..e4b818f 100644 --- a/org/dergods_style_v0.1.org +++ b/org/dergods_style_v0.1.org @@ -49,7 +49,7 @@ with some changes. - A single explicit word describing the file's purpose. - Example of what a source file should look like: ~g_inventory.cxx~. Its corresponding header file should be ~g_inventory.hxx~ and its compilation-generated object file should be ~g_inventory.cxx.o~. In our case, ~g_~ may be described under the main function as gameplay-related. - ~.txt~ format is pointless and forbidden. - - Don't forget a LICENSE and a README. Prefer org-mode or markdown for README if the project is going to be published on platforms such as GitLab or GitHub. Therefore extensions should be ~.org~ or ~.md~. You can add a copy of the README without extension properly formated to be displayed in a terminal. + - Don't forget a LICENSE and a README. Prefer org-mode or markdown for README if the project is going to be published on platforms such as GitLab or GitHub. Therefore extensions should be ~.org~ or ~.md~. You can add a copy of the README without extension properly formatted to be displayed in a terminal. ** Makefile - The project should always contain at least one makefile. -- cgit v1.2.3