diff options
| author | Herbert Thielen <thielen@hs-worms.de> | 2017-08-31 16:12:17 (GMT) |
|---|---|---|
| committer | Herbert Thielen <thielen@hs-worms.de> | 2017-08-31 16:12:17 (GMT) |
| commit | e033d8c73de8d757fa30d22626ae026f43be6bd5 (patch) | |
| tree | 212d2754181daeaa3aa85964637f5bf3b3b50842 /googlemock/docs | |
| parent | a430e9c176bd78d5deed693b1239dc96c95a1ec2 (diff) | |
| download | googletest-e033d8c73de8d757fa30d22626ae026f43be6bd5.zip googletest-e033d8c73de8d757fa30d22626ae026f43be6bd5.tar.gz googletest-e033d8c73de8d757fa30d22626ae026f43be6bd5.tar.bz2 | |
change links from former code.google.com to current github repositoryrefs/pull/1241/head
Diffstat (limited to 'googlemock/docs')
| -rw-r--r-- | googlemock/docs/DevGuide.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/googlemock/docs/DevGuide.md b/googlemock/docs/DevGuide.md index adb74fe..cae07e7 100644 --- a/googlemock/docs/DevGuide.md +++ b/googlemock/docs/DevGuide.md @@ -64,7 +64,7 @@ compile it in the [README](../README.md) file. A mocking framework is of no good if itself is not thoroughly tested. Tests should be written for any new code, and changes should be verified to not break existing tests before they are submitted for -review. To perform the tests, follow the instructions in [README](http://code.google.com/p/googlemock/source/browse/trunk/README) and +review. To perform the tests, follow the instructions in [README](../README.md) and verify that there are no failures. # Contributing Code # @@ -98,7 +98,7 @@ to conform to the style outlined [here](https://google.github.io/styleguide/cppg Please do submit code. Here's what you need to do: 1. Normally you should make your change against the SVN trunk instead of a branch or a tag, as the latter two are for release control and should be treated mostly as read-only. - 1. Decide which code you want to submit. A submission should be a set of changes that addresses one issue in the [Google Mock issue tracker](http://code.google.com/p/googlemock/issues/list). Please don't mix more than one logical change per submittal, because it makes the history hard to follow. If you want to make a change that doesn't have a corresponding issue in the issue tracker, please create one. + 1. Decide which code you want to submit. A submission should be a set of changes that addresses one issue in the [Google Mock issue tracker](https://github.com/google/googletest/issues). Please don't mix more than one logical change per submittal, because it makes the history hard to follow. If you want to make a change that doesn't have a corresponding issue in the issue tracker, please create one. 1. Also, coordinate with team members that are listed on the issue in question. This ensures that work isn't being duplicated and communicating your plan early also generally leads to better patches. 1. Ensure that your code adheres to the [Google Mock source code style](#Coding_Style.md). 1. Ensure that there are unit tests for your code. |