> 1. rm <file> > 2. cvs rm <file> > 3. cvs diff ... > > don't worry about "cvs commit"... whoever decides to commit (and has commit > rights) will take care of that step...
Thanks for that. I will save this email. > can you email the diff to yourself and apply it? if that doesn't work you > probably need to do some setup to make sure your diffs don't get mangled. if > you don't know how to make that happen use alpine for your diffs (on openbsd > it is patched by default to send diffs that aren't mangled) or just .tar.gz > and send as an attachment... Did you have problem patching? I have no problem because I use patch -l (lowercase ell) and also I attached the patch itself + inline diff. I will attach as tar.gz then. > in terms of the diff > (1) please replace kurt as maintainer with myself. sure > (2) did you test with the framework that you mentioned that had problems? > what were the results? Stanse, defect tracking. Nope it didn't work. I have to figure out where it is getting some GCC preprocessor stuff in Java. WIP. > (3) did you try to build any dependencies on openbsd? i would at least try to > build jdk1.7, libreoffice and maybe one or two of the smaller dependencies. > please report any breakage. Nope, I didn't try. Will do it this weekend. What small packages you want me to test out? I can grep but if you know off the top or have a preference, please let me know. Thanks
