From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1OkJTu-000439-2L for garchives@archives.gentoo.org; Sat, 14 Aug 2010 16:21:14 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 71FABE073C; Sat, 14 Aug 2010 16:21:10 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 138AAE01BE for ; Sat, 14 Aug 2010 16:21:06 +0000 (UTC) Received: from marsupilami.localnet (84-238-115-127.u.parknet.dk [84.238.115.127]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPSA id 61B1D1B4044 for ; Sat, 14 Aug 2010 16:21:05 +0000 (UTC) From: Thilo Bangert Organization: Gentoo To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in media-libs/mlt: ChangeLog mlt-0.5.4-r1.ebuild Date: Sat, 14 Aug 2010 18:19:38 +0200 User-Agent: KMail/1.13.5 (Linux/2.6.35.1; KDE/4.4.5; i686; ; ) References: <20100806212139.9E8422CE15@corvid.gentoo.org> <20100814142944.GA15913@Mystical> <4C66BF60.8050902@gentoo.org> In-Reply-To: <4C66BF60.8050902@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2592068.Gp2tlkTTaA"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201008141819.41090.bangert@gentoo.org> X-Archives-Salt: c18cc11e-f2df-4779-b2ff-693d12e031b1 X-Archives-Hash: bf6fdb1606629a034dd52797242d3da5 --nextPart2592068.Gp2tlkTTaA Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Richard Freeman said: > On 08/14/2010 10:29 AM, Markos Chandras wrote: > > So do I. Fixing your package and you don't even bother to send a > > *ready to go* patch upstream seems like a bit rude to me as well. > > Perhaps, we do have a complete different point of view in this one. > > Recent example is Ch=C3=AD-Thanh Christopher Nguy=E1=BB=85n who thanked= me for > > fixing his package, asked me to attach the patch so *he* can send it > > upstream. I thought that was the *default* policy. Anyway. I should > > talk to each maintainer separately when I fix his package. Seems to > > me is the best approach >=20 > My two cents. In my opinion, whether a commit is good or not depends > on whether it left Gentoo as a whole in better or worse shape than > before it was made. >=20 > Here it sounds like we had QA problems before the commit, and no QA > problems after the commit. Maybe the maintainer has some work to do > now, but he had it to do anyway, and the maintainers have less work to > do now than they did before the patches were made. >=20 > Now, if he had broken something due to a sloppy commit I'd be more > concerned. >=20 > Many hands make for lighter work. The best way to have many hands is > to make individual tasks easier. 1+1+1+1+1 is going to happen faster > than 3+2, since nobody ever gets around to doing 3. >=20 > If we give devs an ultimatum like "fix it all or don't fix anything" > guess which one they'll pick? exactly. maybe the maintainer has to do some catch up work, but thats ok.=20 the aim is to improve the tree and not for QA to do the work of the=20 maintainer. perhaps there is a lesson here though: if the bug isnt closed as soon as=20 the patch has hit the tree, but its subject changed to 'push QA patch=20 upstream', then it is clear what is left to do. >=20 > Rich --nextPart2592068.Gp2tlkTTaA Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) iEYEABECAAYFAkxmwh0ACgkQxRElEoA5Ane+AgCeIgU0yis7SuuGPbfkovg/mXbj aPQAoJOVPGeRgqaRplvd15UBUcKKkILk =qnLx -----END PGP SIGNATURE----- --nextPart2592068.Gp2tlkTTaA--