On 10/8/07, Sean O'Rourke <[EMAIL PROTECTED]> wrote: > Peter Dyballa <[EMAIL PROTECTED]> writes: > > > Am 07.10.2007 um 20:43 schrieb Sean O'Rourke: > > > >> What's the best way to track CVS?
Hi, I haven't had time to pursue it just now, but I still have some hope that Emacs.app might make it into GNU CVS, making things a LITTLE easier. (Problems like that affecting the Carbon port right now will still come up of course.) In the meantime Peter's second approach is best (use rc2a big tarball + "cvs up"). You'll get occasional conflicts, but that's easier than unpatch-up-repatch. As far as my own changes, I post important patches to Sourceforge. (There's one for rc2a now.) My releases are not frequent, but in truth I don't do that much in between anyway -- usually a release consists of doing a lot of work in the two weeks just before it. Re: "local changes to NS-specific files", I highly encourage you to post these to the list. I'll incorporate them as I can, and this would definitely help me make faster releases. While public VC is good for high-volume, many-contributor projects, there's currently no need for Emacs.app itself to be in CVS for distributed development to happen. Adrian ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Emacs-app-dev- mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emacs-app-dev-
