From mint-bounce@lists.fishpool.fi Tue Oct 14 14:07:53 2008 Message-ID: <48F4DEF0.5010703@atari-source.org> Date: Tue, 14 Oct 2008 14:03:28 -0400 From: Mark Duckworth User-Agent: Thunderbird 2.0.0.17 (Macintosh/20080914) MIME-Version: 1.0 To: Alan Hourihane CC: mint Subject: Re: [MiNT] Development References: <1224004304.13924.199.camel@jetpack.demon.co.uk> In-Reply-To: <1224004304.13924.199.camel@jetpack.demon.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: mduckworth@atari-source.org Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Alan Hourihane wrote: > In an effort to increase visibility between developers, is there any > chance the other developers on this list can get access to the FreeMiNT > CVS ?? > > What I'm thinking is that I'd like to get my changes onto a branch > within the FreeMiNT CVS, so that others can see the work, and possibly > help test/debug it. > > That way when it's deemed "good", it can be merged to the trunk for the > main release. > > This is a way a lot of open source development processes work, and > should allow others to see new developments and comment more readily. > > Comments ? > > Alan. > > > > Seems good. It would be nice to be able to work off of CVS once I start my changes, but I'm talking about such major changes that I'd probably develop independently just to get going. PS: My 4.4BSD book arrived today. Looks fantastic. Thanks, Mark