For the new files, cvs add them to your local repository. This doesn't add them to the server but lets cvs know about them. Then do "cvs diff -u2 -N" over your tree. The "-N" means "include new files in the diff". Attach this text file to the bug.
Next, zip up any binaries (nibs, images, etc) into a single zip file and attach that separately.
Note that we probably won't get to this until Camino 0.9. You should keep us appraised of your status in the bug so that we can iterate on the design and appearance while you're working. That should hopefully save you from having to go back and re-do chunks after doing a lot of work.
Do you have any shots of what you want it to look like when it's done? Maybe you can work with Jasper.
On Feb 24, 2004, at 1:27 AM, Geoff Beier wrote:
1. diffs to existing source files (I assume cvs diff -u)
2. new source files and the corresponding changes to the related project files
3. changes to .nibs
-- Mike Pinkerton Mac Weenie [EMAIL PROTECTED]
_______________________________________________ Camino mailing list [EMAIL PROTECTED] http://mozdev.org/mailman/listinfo/camino
