From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22409 invoked by alias); 2 May 2004 15:05:27 -0000 Mailing-List: contact mauve-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: mauve-discuss-owner@sources.redhat.com Received: (qmail 22371 invoked from network); 2 May 2004 15:05:26 -0000 Received: from unknown (HELO smtpq2.home.nl) (213.51.128.197) by sources.redhat.com with SMTP; 2 May 2004 15:05:26 -0000 Received: from [213.51.128.132] (port=35583 helo=smtp1.home.nl) by smtpq2.home.nl with esmtp (Exim 4.30) id 1BKIWz-0006SB-M3 for mauve-discuss@sources.redhat.com; Sun, 02 May 2004 17:05:25 +0200 Received: from cc68231-a.ensch1.ov.home.nl ([212.120.112.227]:35653 helo=dumas.thomas.planescape.com) by smtp1.home.nl with esmtp (Exim 4.30) id 1BKIWx-0003lv-MJ for mauve-discuss@sources.redhat.com; Sun, 02 May 2004 17:05:23 +0200 From: Thomas Zander To: mauve-discuss@sources.redhat.com Subject: Re: patch committal. Date: Sun, 02 May 2004 15:05:00 -0000 User-Agent: KMail/1.6.2 References: <200405021416.35670.zander@javalobby.org> <16532.61022.809686.215004@cuddles.cambridge.redhat.com> In-Reply-To: <16532.61022.809686.215004@cuddles.cambridge.redhat.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200405021704.12662.zander@javalobby.org> X-AtHome-MailScanner-Information: Please contact support@home.nl for more information X-AtHome-MailScanner: Found to be clean X-SW-Source: 2004-q2/txt/msg00064.txt.bz2 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 02 May 2004 14:49, Andrew Haley wrote: > Thomas Zander writes: > > I've requested a cvs account several times; but have not even > > received the courtesy of a yes/no answer. > > We should get you a CVS account. However, your opinion that "its more > important to have people creating patches and moving the project > forward then to always have a 100% correct CVS" makes people worried. That statement was discussed and I learned that mauve does not have any=20 sort of release cycle in which bugs can be fixed. Its 'released' as a=20 final product in CVS on a daily basis, so to say. I agree that that takes a slightly different approach. > You should get CVS access, I think,=20 That would be nice; anyone I can contact? > but of course you'll still need to=20 > post patches here for pre-commit discussion. Everybody does that. No problem, if you think that helps :-) > There were problems with your patches. I fixed the problems by hand. > Please don't provide he ChangeLog as a diff: it won't apply anyway. I > have committed both these patches. Please check they're OK. After a CVS update I indeed found no file to be modified anymore. Thanx! - --=20 Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAlQ3pCojCW6H2z/QRAoS9AJwK00dYdrXqsJSZT6YkKEIQn9GfyQCg6jTA bND9ONOOzSpYFiJybbWTmhI=3D =3DGsIw -----END PGP SIGNATURE-----