From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17150 invoked from network); 22 Jul 2004 12:59:17 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 22 Jul 2004 12:59:17 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.34) id 1BndAK-0003vV-93 for arch-gentoo-dev@lists.gentoo.org; Thu, 22 Jul 2004 12:59:16 +0000 Received: (qmail 28625 invoked by uid 89); 22 Jul 2004 12:59:15 +0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 4354 invoked from network); 22 Jul 2004 12:59:15 +0000 From: Chris Gianelloni Reply-To: wolf31o2@gentoo.org To: gentoo-dev@lists.gentoo.org In-Reply-To: <200407221235.03131.carlo@gentoo.org> References: <20040720131405.GW18023@mail.lieber.org> <200407211647.21609.carlo@gentoo.org> <1090443109.19552.145.camel@localhost> <200407221235.03131.carlo@gentoo.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-TP0IobKjdZ9y+tb40Fok" Organization: Gentoo Linux Message-Id: <1090501615.22438.62.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Thu, 22 Jul 2004 09:06:55 -0400 Subject: Re: [gentoo-dev] Revisiting GLEP 19 X-Archives-Salt: 344f7b29-672c-4f4a-abf9-97fa41b910b7 X-Archives-Hash: a2d45fdafe21fb3286da6ed67383c53d --=-TP0IobKjdZ9y+tb40Fok Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2004-07-22 at 06:34, Carsten Lohrke wrote: > I never assumed to write xml by hand - Stuarts email sound a bit like it = - but=20 > even "field1", "field2", ... would be annoying. If echangel= og=20 > would be smart and parse the input, that would be ok. Maybe I got it wron= g,=20 > but I was under the impression that there would be at least one new field= be=20 > introduced, indicating the importance of a bug fix; And a increasing numb= er=20 > of fields wouldn't make parsing input simpler. If using xml doesn't=20 > complicate writing the ChangeLog I'm all for it. What about something like: echangelog Then you make echangelog a bit smart. You could use it in several ways. echangelog "text here" for changes that are made without a bug attached or any additional information. echangelog "text here" "69" for changes that are made to close bug #69. But what if you want to enter but not a bug? Then you would use echangelog "text here" "" "foo" (just an idea). All of this would keep echangelog from getting too complex, while still giving it flexibility. Any better ideas are definitely welcome... =3D] --=20 Chris Gianelloni Release Engineering QA Manager/Games Developer Gentoo Linux Is your power animal a penguin? --=-TP0IobKjdZ9y+tb40Fok Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBA/7vukT4lNIS36YERAtIvAKCpqDZV5vgKElESIRY9OffOWuO5lQCgh9NX RgpGNoQ3jqDlPusbCPFIaoM= =X8VV -----END PGP SIGNATURE----- --=-TP0IobKjdZ9y+tb40Fok--