Fixed some bugs in the parsers. A full features and desires test now works. There are stil some extension support which needs to be added to ptopgen.

Added support for set-type-limits in the advertisement. It is implemented as an extension. There is no support for this in v1. It will only be in v2 and higher. To this end, ptopgen has been modified. ptopgen also now adds type slot information to nodes as an extension. However, support for other extensions still have to be added. Added another annotater class for rspec v2 but this in a very incomplete state as of now and the relevant code has been commented out of solution.cc temporarily. Assign's arguments have also been modified in mapper, so that it expects rspec inputs.

Conflicts:
	tbsetup/libvtop.pm.in

Updated extensions for correct namespaces. Modified makefiles to install different versions of the schemas in different directories. Modified the configure script to do the same thing. xsdgen has been modified as well, although it doesn't seem to have made it to this commit list.

are two ways this can happen.

1. When allocating the proxy nodes before getting the tickets. This is
   just like the local node case; need to go around the loop again and
   retry with a new node set. 

2. When getting the tickets, someone else got the nodes and gthe
   getticket fails. This is a lot like case 1, but now we have to
   nfree the proxy node, and tell the mapper to try again.

attempts by protogeni code.

The toolchain build should be dependent on an actual file to ensure we
don't rebuilt it for every target that goes into the initramfs.

Also rename old fake tcsh to tcsh.fake, and run a new script that
symlinks tcsh and csh to tcsh.fake if tcsh doesn't exist.  This way tcsh
can be removed from the build but tcsh/csh users can still log in.

Conflicts:
	tbsetup/libvtop.pm.in

or more then one experiment, of course.

commit.

use when (re)loading a node.

<disk_image
   name="urn:publicid:IDN+emulab.net+image+GeniSlices//UBUNTU91-LAMP" />

In other words, allow "GeniSlices" for the project, so we can add
images to be used from the rspec.

Use 'git diff-tree --no-commit-id --cc' on merge commits to determine if
there are any differences between the merge commit and its parents.
This is the case if any new files were hand-modified or added as part of
the merge (such as when conflicts were resolved).  If git-diff-tree
produces no output, the merge was trivial.

If the merge was trivial, the commit message is checked for an empty
body.  If empty, the commit is skipped when generating the email.  This
way if the committer documents the merge in some way (list of changes,
reason for the merge, etc.) the email includes that information.