diff options
| author | Thomas Markwalder <tmark@isc.org> | 2019-06-20 13:35:58 -0400 |
|---|---|---|
| committer | Thomas Markwalder <tmark@isc.org> | 2019-06-20 13:35:58 -0400 |
| commit | e82c02c01657c7073392aab0d17e3126c3c9207f (patch) | |
| tree | 252f50ac4545db72441eae1be65b664f41987f1a | |
| parent | 61d8bdd9c35988292b3b194c7d4cbc915aa24d2a (diff) | |
| download | isc-dhcp-e82c02c01657c7073392aab0d17e3126c3c9207f.tar.gz | |
Update CONTRIBUTING.md
| -rw-r--r-- | CONTRIBUTING.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 33c29c02..0231c08c 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -79,7 +79,7 @@ as perceived by the ISC engineer, the issue and/or MR will be assigned to one of ## Merge Request (also known as sending your patch the right way) The first step in writing the patch or new feature should be to get the source code from our Git -repository. The procedure is very easy and is [explained here](https://gitlab.isc.org/isc-projects/dhcp/wikis/gitlab-howto). +repository. The procedure is very easy and is [explained here](https://gitlab.isc.org/isc-projects/dhcp/wikis/processes/gitlab-howto). While it is possible to provide a patch against the latest stable release, it makes the review process much easier if it is for latest code from the Git master branch. |