From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id F207E138A1A for ; Thu, 19 Feb 2015 12:39:43 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 995E1E08E9; Thu, 19 Feb 2015 12:39:36 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 28B65E0852 for ; Thu, 19 Feb 2015 12:39:35 +0000 (UTC) Received: from [192.168.4.8] (ppp-94-67-62-166.home.otenet.gr [94.67.62.166]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: hwoarang) by smtp.gentoo.org (Postfix) with ESMTPSA id 821A134099B for ; Thu, 19 Feb 2015 12:39:33 +0000 (UTC) Message-ID: <54E5D980.5050507@gentoo.org> Date: Thu, 19 Feb 2015 14:39:28 +0200 From: Markos Chandras User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 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 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in eclass: fcaps.eclass References: <20150218161153.58F3C1208D@oystercatcher.gentoo.org> <20150218224827.51621e71@pomiot.lan> <20150219123127.6d11ca63@gentoo.org> <2166603.dPFk90yGng@localhost> <20150219123855.436d4f49@gentoo.org> In-Reply-To: <20150219123855.436d4f49@gentoo.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Archives-Salt: 83825b38-3057-47e8-a5a4-d3752294cada X-Archives-Hash: 809d5fde0d03a2041529dd35d1e0f0e7 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 02/19/15 13:38, Alexis Ballier wrote: > On Thu, 19 Feb 2015 19:34:28 +0800 Patrick Lauer > wrote: > >> On Thursday 19 February 2015 12:31:27 Alexis Ballier wrote: >>> On Wed, 18 Feb 2015 22:48:27 +0100 >>> >>> Michał Górny wrote: >>>> Dnia 2015-02-18, o godz. 16:11:53 >>>> >>>> "Mike Frysinger (vapier)" napisał(a): >>>>> vapier 15/02/18 16:11:53 >>>>> >>>>> Modified: fcaps.eclass Log: clarify >>>>> USE=filecaps intention #540430 >>>>> >>>>> Revision Changes Path 1.11 >>>>> eclass/fcaps.eclass >>>> >>>> Please commit the missing ChangeLog update and remember to >>>> update the ChangeLog after changing any eclass in any way. >>>> This is an official policy for any commits to the Gentoo >>>> repository [1] and a lack of consistency in entries to the >>>> ChangeLog is confusing to our developers and users. >>>> >>>> [1]:http://devmanual.gentoo.org/ebuild-writing/misc-files/changelog/index. >>>> >>>> html >>> this policy is about packages; cvs log is *muuuuch* better than >>> any global changelog for eclasses: who will dig into a >>> thousand changelog entries to find what changed in fcaps.eclass >>> ? >>> >>> if you want changelogs in eclass/, make it per-eclass, like it >>> is already per-package. >>> >> >> We've had this discussion before ... so ... > > > what i remember of it is someone adding a ChangeLog file to eclass/ > and sending an email to ask people to fill it. Mind sharing a link > ? > > I think I'll add ChangeLog to every category and ask people to fill > it whenever they make changes to a package in that category. This > would have the same level of usefulness as a ChangeLog in eclass/. > > Alexis. > We had the same discussion again in the past http://archives.gentoo.org/gentoo-dev/msg_51d268a7757fd90fbda77d373a2664f8.xml and again http://www.gossamer-threads.com/lists/gentoo/dev/262085 we can't keep having the same discussion. The original changelog discussion is here http://archives.gentoo.org/gentoo-dev/msg_c3436497e445eaf86deea087788882e5.xml There were no objections so we started using it http://archives.gentoo.org/gentoo-dev/msg_72fafb93225c9f5559415356eb093f44.xml Can we please bookmark them for future reference? Do we really need to make every single bit of development a formal policy? Do we really need to discuss every single bit of development in the mailing lists? When did we stop being developers because it was a fun thing to do and turned into a bunch of mean people pointing fingers at each other? - -- Regards, Markos Chandras -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCgAGBQJU5dmAAAoJEPqDWhW0r/LCNwQP/3pffbifLk24zHVDh7nlHOxv 2dqggYIro4SxmhaRI2/2gRa/ozdwsu6JjH0+f5taMThvX5OAiJWmQL8u53A/RlO+ xSIN4yPtaDsVbGEzGawvkI4abgFbLx8zNJdOnb2W/hF5JNLAoSZR8RFPeXjbtzw/ sUu1vwL9IilT3jTG8fAutRcdnrYrkFtxO0QkRm11sdYcvgYB1ZBHlepsTmDkFt1v 5DOfm6+iI+ZZsx1K0Avjosl3YmLWu3kyyQeFdaaZN+wgFdk1j+4cZ9qqCeoHJaki ms2F2QwR3mC009aoSgiR8IbSz3UfK/zQ4zLpX2r+7jdO/Fa2ek3IQl7qrLsP8eAJ D2LCPGVi8IKJkpTyFX+YqPsL4/c1Jw0KjnEUIXqYcqxi9G2FP0yZSqsAQHdkEW12 qnDlss5E5rCAltQs53yaJBvpGm0Ziu+OYHY8uSfBIRe3JNolD95FXjp32EhoXGpD N/gaZxhlGgqAasszG3L1XEq9S8uxUU9c1cfCPvzH8Br664cAyHtM5tZnQjbP+e/S jO9caZC3Ummodj/RFU9MIFdBAuLUqZw9bTGkuN8KwqUcbXl+LeFsuHf9Ys4NYMlh EouE/+avI1y3WqO7M/kBFVJhS7pqoyCQym3NOzyj3IbsaMG6y3T2iC6XOc3SL1NU hFswjFA038/x+xnogfvk =qdEX -----END PGP SIGNATURE-----