aboutsummaryrefslogtreecommitdiff
path: root/DEVELOPING
diff options
context:
space:
mode:
authorSteve Bennett <steveb@workware.net.au>2011-04-12 17:32:50 +1000
committerSteve Bennett <steveb@workware.net.au>2011-06-10 14:00:12 +1000
commit5233ba4aafc1b8a5fca412001e047760333aff8e (patch)
tree2417aabaedbc05f57a9cb9a580c4a828a67cbcd5 /DEVELOPING
parentc8392364cc98e5cfb371b62a8df0e7ff8d575e5e (diff)
downloadjimtcl-5233ba4aafc1b8a5fca412001e047760333aff8e.zip
jimtcl-5233ba4aafc1b8a5fca412001e047760333aff8e.tar.gz
jimtcl-5233ba4aafc1b8a5fca412001e047760333aff8e.tar.bz2
Update TODO to reflect the current state of Jim
Signed-off-by: Steve Bennett <steveb@workware.net.au>
Diffstat (limited to 'DEVELOPING')
-rw-r--r--DEVELOPING5
1 files changed, 2 insertions, 3 deletions
diff --git a/DEVELOPING b/DEVELOPING
index 20f0a4a..42fb054 100644
--- a/DEVELOPING
+++ b/DEVELOPING
@@ -46,7 +46,7 @@ the project that is about to be started. The only thing that has to be
taken care of is the project mode -- it should be "push mode".
Once the project is created one must add a user that will actually
-start commiting new files to the repo. It can also be done throught
+start commiting new files to the repo. It can also be done through the
WWW interface, so nothing more is necessary.
Once finished with setting up a project on the WWW panel, one can
@@ -88,7 +88,6 @@ submitting patches, you can verify that your changes didn't bring any
regressions to the Jim. In order to do so, sample regression tests have
been implemented. You can execute them by typing:
- cd tests
- make
+ make test
All tests should succeed.