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 1RJ7uz-0003Ka-Ll for garchives@archives.gentoo.org; Wed, 26 Oct 2011 18:09:37 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6EEA821C049; Wed, 26 Oct 2011 18:09:03 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id E0CC021C25F for ; Wed, 26 Oct 2011 18:07:38 +0000 (UTC) Received: from [192.168.1.35] (40.red-80-29-60.adsl.static.ccgg.telefonica.net [80.29.60.40]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: pacho) by smtp.gentoo.org (Postfix) with ESMTPSA id 95F021B401A for ; Wed, 26 Oct 2011 18:07:37 +0000 (UTC) Subject: Re: [gentoo-dev] [Council] ChangeLog generation within Gentoo From: Pacho Ramos To: gentoo-dev@lists.gentoo.org In-Reply-To: <20111026193356.058efef7@neptune.home> References: <20111026170212.GD843@gentoo.org> <20111026193356.058efef7@neptune.home> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-TTlEt21LH1xSZIlDssl6" Date: Wed, 26 Oct 2011 20:07:33 +0200 Message-ID: <1319652453.5300.10.camel@belkin4> 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 X-Mailer: Evolution 2.32.3 X-Archives-Salt: X-Archives-Hash: 1cd36552c35b5163472a924b06d8dafb --=-TTlEt21LH1xSZIlDssl6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable El mi=C3=A9, 26-10-2011 a las 19:33 +0200, Bruno escribi=C3=B3: > On Wed, 26 October 2011 Fabian Groffen wrote: > > However, this also allows to do all kinds of other actions to the > > ChangeLog file, without actually adding an entry for the current change > > being committed, as we've already seen in practice. > > The Council would like to remind developers that it is still a > > requirement that all actions are documented in the ChangeLog and that i= t > > is hence the responsibility of the committing developer to make sure > > this requirement is met. >=20 > Is there some guideline about old entries in the ChangeLog? >=20 > Over the past months ChangeLogs represent a big part of the tree, some > of them being pretty big and going back many changes (hundreds of them) > and years (even for actively maintained ebuilds). >=20 > In order to not bloat the tree I would like to see old entries purged > when there are more than 25-50 of them, especially if they refer to > ebuilds gone since more than 3-6 months. > Someone in need for long gone ebuild would have to look at VCS anyhow, so > looking at ChangeLog/history over there would seem logical. >=20 > On a compressed tree (squashfs) dropping all ChangeLogs reduces size from > ~55MiB to around 35MiB which is quite a lot! >=20 > Bruno >=20 >=20 Personally, I want to have full ChangeLog easily accessible, I remember to need to look for really old entries when becoming a new maintainer for an old package previously maintained by others. What I don't know is the reasons for not compressing ChangeLogs by default (well, I don't have a compressed tree, this probably won't be a gain for people using it) --=-TTlEt21LH1xSZIlDssl6 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iEYEABECAAYFAk6oTGUACgkQCaWpQKGI+9Ra+ACfdle7oN/pqP0DiI1KYmgP4OWb GFYAn2S20W3AD0a7p+5elaRvFqWFXgzS =rQGU -----END PGP SIGNATURE----- --=-TTlEt21LH1xSZIlDssl6--