|Account Administration (Grades, Registration, etc.)||General Course Information|
|Please take our background survey|
|About the Staff||Materials from the TAs|
|Lecture notes||Labs and Homework|
|Piazza Newsgroup||Frequently Asked Questions|
|Java Library Documentation (also: no frames)||Emacs Quick Guide|
|Tool Documentation: Subversion, Emacs, etc.||A Java Reference.|
|Data Structures (Into Java)||UCB Package Documentation|
|List of instructional login servers||Some data-structure visualizations and a Wikibook.|
|Some project style guidelines||A collection of bad Java practices|
|Berkeley Programming Contests||Downloading Java.|
pretest proj0 or pretest tags/proj0-Nwhich checks out your latest version of proj0 (in $MYREPOS/proj0 or $MYREPOS/tags/proj0-N) and runs a sanity check over it (does it compile; does it run your own tests successfully; does it execute on a trivial file; does it pass the style check?). This looks ONLY at the repository. Uncommitted stuff sitting in your current working directory is ignored (just as the autograder will ignore it).
hwcommand on the instructional machines to submit homework, get homework skeletons, and save versions of your work on an assignment (so as to minimize the damage if you accidentally lose your files).
bug-submitto submit problems with your programs. In a directory containing all the files in your assignment (not just the subdirectory containing the you thing is the problem), prepare a file called ERROR containing a description of your problem and the commands needed to reproduce the problem (this last is important.) Then issue
bug-submit ASSIGNMENTwhere ASSIGNMENT is the name of the assignment (e.g., proj1).
graph-demoon the instructional machines. There are some sample files in directory /home/ff/cs61b/code/graph-demos.