From a8469b7652762ce16bfdaa28b5764febc38d44cb Mon Sep 17 00:00:00 2001 From: shiqian Date: Wed, 16 Jul 2008 23:06:22 +0000 Subject: [PATCH] Edited wiki page through web user interface. --- wiki/GoogleTestDevGuide.wiki | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/wiki/GoogleTestDevGuide.wiki b/wiki/GoogleTestDevGuide.wiki index 24539c96f..4482ee4fa 100644 --- a/wiki/GoogleTestDevGuide.wiki +++ b/wiki/GoogleTestDevGuide.wiki @@ -105,7 +105,9 @@ Please do submit code. Here's what you need to do: # Ensure that your code adheres to the [#Coding_Style Google Test source code style]. # Ensure that there are unit tests for your code. # Sign a Contributor License Agreement. - # Attach the code to the issue it addresses. For brand new files, attach the whole file. For patches to existing files, attach a Subversion diff (that is, `svn diff`). + # Make sure there is an issue in the issue tracker that your change addresses. If necessary, create a new issue. + # Create a patch file using `svn diff`. + # We use [http://codereview.appspot.com/ Rietveld] to do web-based code reviews. You can read about the tool [http://code.google.com/p/rietveld/wiki/CodeReviewHelp here]. When you are ready, upload your patch via Rietveld and notify `googletestframework@googlegroups.com` to review it. There are several ways to upload the patch. We recommend using the [http://codereview.appspot.com/static/upload.py upload.py] script. === Google Test Committers ===