summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTor Aamodt <[email protected]>2012-06-02 18:18:54 -0800
committerAndrew Boktor <[email protected]>2014-08-14 13:47:32 -0700
commit7f9189c1970d1a1d1d007f55d54923b48cccc545 (patch)
tree3f641124c5ca76dca846516a4cd34fd86ac79e69
parent7edfd64a2b39222d7424d2b6c0f14a68fe1903ed (diff)
minor update to README
[git-p4: depot-paths = "//depot/gpgpu_sim_research/fermi/distribution/": change = 12906]
-rw-r--r--README8
1 files changed, 5 insertions, 3 deletions
diff --git a/README b/README
index cd3b659..5425c64 100644
--- a/README
+++ b/README
@@ -258,6 +258,8 @@ they may have changed. Assuming the code compiles without errors/warnings the
next step is to do some regression testing. At UBC we have an extensive set of
regression tests we run against our internal development branch when we make
changes. In the future we may make this set of regression tests publically
-available. For now, you will want to compile and re-run all of the applications
-you care about before making further changes to identify if any runtime errors
-that occur.
+available. For now, you will want to compile the merged code and re-run all of
+the applications you care about (implying these applications worked for you
+before you did the merge). You want to do this before making further changes to
+identify any compile time or runtime errors that occur due to the code merging
+process.