Welcome to EE464 Trac page
We can document each of our modules on the wiki and then we can add links to them from this page. So once you've started work on your module, please start documenting it in the wiki. If you're having trouble editing the wiki pages, see WikiFormatting and TracLinks for help.
Trac Links
Here's a quick guide to using TracLinks. These links can be used in your commit messages or wiki pages, and they link directly to other parts of the Trac system. Links can point to tickets, reports, changesets, milestones, source files and other Wiki pages. Since I've set up InterTrac, please use the following notations, so that way the SVN commit email notifications links will work properly.
* Tickets: 464:ticket:1 * Reports: 464:report:1 * Changesets: 464:changeset:1 * ...
Display:
- Tickets: 464:ticket:1
- Reports: 464:report:1
- Changesets: 464:changeset:1
- ...
LaTeX
We're going to use LaTeX for all of our papers because it provides pretty good formatting, but the other really nice feature is we can use the SVN repository to manage the versions of the document and collaborate easier.
Coding Standards
If you're going to program, read them: Coding Standards
Subversion
The server is using Subversion version 1.5 so make sure your client is 1.5+ otherwise it will not work properly! To check out do: svn co http://svn.hydndesigns.com/464.
Tips:
- BIG NOTE: Trunk is for stable code only, if you knowingly commit broken code to trunk, you will get the smack. Leave all your development in branches.
- BIG NOTE the second: Do not check in a binary file! An exception is a pdf that will not change (i.e. external documentation). The other exception is a Powerpoint presentation.
- Subversion uses "atomic" revisions which means all your files in your present working directory and down will be checked in at once.
- Notice "present working directory and down" which means if you're working on papers, don't commit to 464/trunk, do the commit in 464/trunk/doc.
- You might want to set an environment variable to make things like branching or merging easier.
- For example, instead of having to type http://svn.hydndesigns.com/464 every time, you could set $SVN_REPO to that.
- If you're on the PS3 and you don't want to use the -m flag to put a message set your $SVN_EDITOR to vim or w/e. Ubuntu usually sets this to vim by default, but Yellow Dog doesn't. (e.g. export SVN_EDITOR=vim)
