From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15975 invoked by alias); 2 May 2004 23:49:20 -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 15967 invoked from network); 2 May 2004 23:49:19 -0000 Received: from unknown (HELO ms-smtp-02-eri0.southeast.rr.com) (24.25.9.101) by sources.redhat.com with SMTP; 2 May 2004 23:49:19 -0000 Received: from [10.0.0.2] (rdu57-9-048.nc.rr.com [66.57.9.48]) by ms-smtp-02-eri0.southeast.rr.com (8.12.10/8.12.7) with ESMTP id i42NnFkF025739; Sun, 2 May 2004 19:49:16 -0400 (EDT) Subject: Re: patch committal. From: "C. Brian Jones" Reply-To: cbj@gnu.org To: Thomas Zander Cc: mauve-discuss@sources.redhat.com In-Reply-To: <200405021704.12662.zander@javalobby.org> References: <200405021416.35670.zander@javalobby.org> <16532.61022.809686.215004@cuddles.cambridge.redhat.com> <200405021704.12662.zander@javalobby.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-3E+am7+X8mCH5DeZxhDu" Message-Id: <1083541755.3175.108.camel@lyta.haphazard.org> Mime-Version: 1.0 Date: Sun, 02 May 2004 23:49:00 -0000 X-Virus-Scanned: Symantec AntiVirus Scan Engine X-SW-Source: 2004-q2/txt/msg00065.txt.bz2 --=-3E+am7+X8mCH5DeZxhDu Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Content-length: 1500 On Sun, 2004-05-02 at 11:04, Thomas Zander wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > 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. >=20 > 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. >=20 > > You should get CVS access, I think,=20 > That would be nice; anyone I can contact? >=20 > > 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 :-) >=20 > > 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. >=20 > After a CVS update I indeed found no file to be modified anymore. Thanx! Tom Tromey can get you access. Mauve has a fairly relaxed commit policy, basically adding/fixing tests good, changing anything else requires discussion. Brian --=-3E+am7+X8mCH5DeZxhDu Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part Content-length: 189 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQBAlYj7cEcmdY33uzYRAia8AJ0Zy6zkLVgiie+X8QviGJI2eaTdQACeLwpn qDNFfNSA24nymg1+uVm8ZUc= =SQpF -----END PGP SIGNATURE----- --=-3E+am7+X8mCH5DeZxhDu--