From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28259 invoked by alias); 15 Jan 2014 20:57:50 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 28201 invoked by uid 89); 15 Jan 2014 20:57:49 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.3 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 X-Spam-User: qpsmtpd, 2 recipients X-HELO: smtp.gentoo.org Received: from smtp.gentoo.org (HELO smtp.gentoo.org) (140.211.166.183) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Wed, 15 Jan 2014 20:57:46 +0000 Received: from vapier.localnet (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 1147233ED47; Wed, 15 Jan 2014 20:57:45 +0000 (UTC) From: Mike Frysinger To: Eli Zaretskii Subject: Re: small request regarding commits in binutils-gdb.git Date: Wed, 15 Jan 2014 20:57:00 -0000 User-Agent: KMail/1.13.7 (Linux/3.12.1; KDE/4.6.5; x86_64; ; ) Cc: fred.cooke@gmail.com, gdb-patches@sourceware.org, brobecker@adacore.com, binutils@sourceware.org References: <20140115121251.GM4639@adacore.com> <201401151502.09189.vapier@gentoo.org> <83y52h2d5x.fsf@gnu.org> In-Reply-To: <83y52h2d5x.fsf@gnu.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2120359.hdqArfjxqX"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201401151557.48453.vapier@gentoo.org> X-IsSubscribed: yes X-SW-Source: 2014-01/txt/msg00564.txt.bz2 --nextPart2120359.hdqArfjxqX Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-length: 1067 On Wednesday 15 January 2014 15:38:50 Eli Zaretskii wrote: > > From: Mike Frysinger > > Date: Wed, 15 Jan 2014 15:02:07 -0500 > > Cc: gdb-patches@sourceware.org, > >=20 > > Eli Zaretskii , > > Joel Brobecker , > > binutils > >=20 > > there's no reason the dist steps can't autogenerate a full ChangeLog > > from git history and throw it into the tarball. it's what other GNU > > projects are doing now (like coreutils). >=20 > If we are going to generate ChangeLog files, this discussion is still > relevant, since the text needs to be formatted according to ChangeLog > rules. not necessarily. there's two options: - just use `git log --stat` and pipe it into a ChangeLog. this isn't a=20 "GNU ChangeLog", but it is a ChangeLog - use the abbreviated commit messages that the tools rely on to create a=20 GNU ChangeLog format obviously i'd prefer the first, but i can live with the second. it's still= way=20 better than hand maintaining ChangeLog files themselves. -mike --nextPart2120359.hdqArfjxqX Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. Content-length: 836 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iQIcBAABAgAGBQJS1vZMAAoJEEFjO5/oN/WBOacQALti2UGanzDjQv/qur4VmOaC KIZSKkqzJkFnAHSeqS26Iw1hb7eHZnwThPus8E2bXjTA1Zzt4zDIvf5srkvvN/I/ ptDLvb9Vd4AhDx144Go64BXqw6gxy9Hiiuj8RmRpDjAN/5+RXRYtMXAySo8QIqDi /zq4Z/oCQ1/B8d4gCeGUcvgYcN8dLbVFSCRGPzpjHwhei7rFBHZV9vVRU91uigfR gwJtsHEbuFAQDr8eUERrpoVrIDG/UvO07GzqiAusOHka6Xn9Hg43TgFS2SPx+XO3 OKlQcO2fwjT4vle9Q8J29ePQvchMazuYUfLlJUrUcQtxNn7wEb6FUH8YySWYBMAD a1PNdGImDzwFFojfTOXJvqignCQb5pM0+VqAEpSAZ2kTrRWphTutjGv/ro55VkZr I16cSpemQim3BE521kG11WZyG23VDofnj3qWdqp50t7iKbiMaGyjBRj2CMlV13Gc 5RbDPbbuEV3PxEkOuzx8xexwqIUjjjSTUKPzKQyOpgoQSRIKzn09oC3oENj6Rqz+ PP1ZV4neaVjcXxceO5GyBa//4lb+TSxUmwEhdg1roaW1V8Vkbyk8IurJ8NPKijSp PFfYb6JozQmtC330gOP/IiuV1aDhtZL/Bd75nKb4HYK6e+YM5V+Nd3yvHO97slXl 1IrWsELyZWsD1DVqn98U =AdNj -----END PGP SIGNATURE----- --nextPart2120359.hdqArfjxqX--