aboutsummaryrefslogtreecommitdiff
path: root/.file-metadata
diff options
context:
space:
mode:
authorMohammad Akhlaghi <mohammad@akhlaghi.org>2019-07-26 13:57:35 +0100
committerMohammad Akhlaghi <mohammad@akhlaghi.org>2019-07-26 14:02:58 +0100
commit33820ab02bd39faa10fe634dfd0de85764e1e96e (patch)
treec098f1dda0bc091076cfa8c6d13ca9d010625063 /.file-metadata
parent23e26355b11ce562dc7f9c4ad85b78e4b7c60f83 (diff)
Better explanation of suggested commit messages in REAME-hacking.md
Until now the description of the commit message guidelines wasn't clear enough and could cause confusion, in particular because it didn't describe why some basic formatting issues are mandatory. With this commit, it is explained that the main reason we require contributors for follow this format is "consistency" within the project. Also generally it was edited to become more elaborate and explain the points more clearly. I also ran a spell check over the whole file and fixed a few typos. This correction was suggested by Mohammad-reza Khellat.
Diffstat (limited to '.file-metadata')
-rw-r--r--.file-metadatabin6106 -> 6106 bytes
1 files changed, 0 insertions, 0 deletions
diff --git a/.file-metadata b/.file-metadata
index 1954e94..af859e9 100644
--- a/.file-metadata
+++ b/.file-metadata
Binary files differ