https://git.reactos.org/?p=reactos.git;a=commitdiff;h=f9dd6dbe6dca0d4793838b...
commit f9dd6dbe6dca0d4793838bf016f358a267b17502 Author: Alexander Shaposhnikov sanchaez@reactos.org AuthorDate: Thu Mar 22 10:49:01 2018 +0200 Commit: GitHub noreply@github.com CommitDate: Thu Mar 22 10:49:01 2018 +0200
[CONTRIBUTING] Clean accidental garbage
Addendum to f50f983f451e3df2e9bab55853f089755164c92b --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 3cbab7b9f7..49a1837d4e 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -65,7 +65,7 @@ Our commit style is defined in a __[commit template]__. Use it as a reference or
- *Use your __real name__ and __real email__.* We do not accept anonymous contributions! - *Ensure your contribution is properly described.* Include the relevant issue number if applicable. -- *Put only related changes.* It will make reviewing easier as the reviewer needs to recall less information about the existing source code that is changed./rapps-db/commit/7737182148cde7c559fb21170d3e5c3acf42648c.patch +- *Put only related changes.* It will make reviewing easier as the reviewer needs to recall less information about the existing source code that is changed. - *Search for similar pull requests/patches before submitting.* It may be that a similar pull request or issue was opened previously. Comment and review on that one instead. - *Keep your contribution small and focused on the topic.* It can be tempting to fix existing issues as you come across them while reading the source code. Resist the temptation and put in a note in the source code instead, or (even better) put the issue in the issue tracking system. - *Respect our __[Coding Style]__ and __[Programming Guidelines]__.*
-
Alexander Shaposhnikov