diff options
| author | Johnny Willemsen <jwillemsen@remedy.nl> | 2015-12-02 11:01:16 +0100 |
|---|---|---|
| committer | Johnny Willemsen <jwillemsen@remedy.nl> | 2015-12-02 11:01:16 +0100 |
| commit | 60b26c84f24e4f2abfff64a8642a49bb700a10e1 (patch) | |
| tree | 20dd67c599657623c49b485963451010bbaac656 | |
| parent | 5444deb74872256b158cc66f35836c81cb92c071 (diff) | |
| download | ATCD-60b26c84f24e4f2abfff64a8642a49bb700a10e1.tar.gz | |
Corrected link to coding guidelines
* README.md:
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md index 4e1041a6a0b..3a0d3c60dbd 100644 --- a/README.md +++ b/README.md @@ -316,7 +316,7 @@ Sometimes work on your topic branch may include several commits. For example, co Also, it is important to make sure you don't accidentally commit files for which no real changes have happened, but rather, whitespace has been modified. This often happens with some IDEs. `git diff --check` should be run before you issue such a pull request, which will check for such "noise" commits and warn you accordingly. Such files should be reverted and not be committed to the branch. -Adhering to [ATCD's code style](https://github.com/DOCGroup/ATCD/blob/master/doc/Coding.txt) guidelines will help minimise "noise" commits. Project Admins are going to ask contributors to reformat their code if necessary. +Adhering to [ATCD's code style](http://htmlpreview.github.io/?https://github.com/DOCGroup/ATCD/blob/master/ACE/docs/ACE-guidelines.html) guidelines will help minimise "noise" commits. Project Admins are going to ask contributors to reformat their code if necessary. ## Keeping your repo in sync with upstream |