X-Git-Url: https://pintos-os.org/cgi-bin/gitweb.cgi?p=pintos-anon;a=blobdiff_plain;f=doc%2Flocalsettings.texi;h=4f061595d860e446bad1a7f4de1865458ab0d23f;hp=6a3dc3ee4b7dff52a58de345de7b5b9a0118d23e;hb=3edcfedb8e62970f3293fa676b6691f8658c3c11;hpb=d158a7cd545fa8dd35dba91935029465eedff0da

diff --git a/doc/localsettings.texi b/doc/localsettings.texi
index 6a3dc3e..4f06159 100644
--- a/doc/localsettings.texi
+++ b/doc/localsettings.texi
@@ -5,6 +5,9 @@
 @set localpintoshttppath http://@/www.stanford.edu/@/class/@/cs140/@/pintos/@/pintos.@/tar.gz
 @set localpintosbindir /usr/class/cs140/`uname -m`/bin
 
+@set recommendvnc
+@clear recommendcygwin
+
 @macro localmachines{}
 The CS 140 ``officially supported'' Pintos development machines are
 the machines in Sweet Hall managed by Stanford ITSS, as described on
@@ -54,8 +57,7 @@ inspired your own in your design documentation.
 
 @macro localcvspolicy{}
 Instead, we recommend integrating your team's changes early and often,
-using a source code control system such as CVS (@pxref{CVS}) or a
-group collaboration site such as SourceForge (@pxref{SourceForge}).
+using a source code control system such as CVS (@pxref{CVS}).
 This is less likely to produce surprises, because everyone can see
 everyone else's code as it is written, instead of just when it is
 finished.  These systems also make it possible to review changes and,
@@ -71,3 +73,6 @@ reviewing that document.  We expect code at the ``Peer-Review Quality''
 level described there.
 @end macro
 
+@macro localdevelopmenttools{}
+@c Descriptions of additional, local development tools can be inserted here
+@end macro