Hi Mario,
looks pretty good!
It'd be awesome if along with all those documents there was a
webrev [1] for your changes.
In your case it'd be a webrev between a repo with your
changes vs jdk7 master (assuming your repo is synced with
master so that the webrev doesn't show any changes other
than ones you made).
It makes it easier to go over the changes quickly..
If your repo's default parent is (some child of) jdk7
master, then all you need to do is run
webrev -l -f
and post a link to the generated webrev/ directory..
Thanks,
Dmitri
[1] http://blogs.sun.com/jcc/entry/webrev_for_openjdk_a_code
http://blogs.sun.com/jcc/resource/webrev
Mario Torre wrote:
Dear judges, dear mailing list,
Please find all necessary material (documentation, source code, tests,
etc) to the Caciocavallo project here:
http://hg.openjdk.java.net/caciocavallo/caciocavallo/raw-file/tip/cacio-docs/index.html
All the source code developed as part of this project is published
under the SCA of Roman Kennke, Mario Torre and aicas GmbH. This
includes the code published under these repositories:
http://hg.openjdk.java.net/caciocavallo/caciocavallo/
http://kennke.org/~hg/hgwebdir.cgi/caciocavallo/
http://kennke.org/~hg/hgwebdir.cgi/caciocavallo-ng/
The latter two serve as prototypical implementations of a GUI
backend. They share some code with the Escher peer from GNU
Classpath. The authors (Mario and me) donated a previous version of that
code to the
GNU Classpath project. The authors made sure that only code is
contributed to any project that was actually written 100% by the
authors.
Kind regards, Mario and Roman
