From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.33) id 1CHUdG-0004Y3-A1 for mharc-grub-devel@gnu.org; Tue, 12 Oct 2004 17:56:34 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CHUdE-0004XM-G2 for grub-devel@gnu.org; Tue, 12 Oct 2004 17:56:32 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CHUdE-0004XA-6m for grub-devel@gnu.org; Tue, 12 Oct 2004 17:56:32 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CHUdD-0004X7-UG for grub-devel@gnu.org; Tue, 12 Oct 2004 17:56:31 -0400 Received: from [193.45.208.6] (helo=griffin.skarpodata.com) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1CHUUw-00007F-Kp for grub-devel@gnu.org; Tue, 12 Oct 2004 17:47:59 -0400 Received: from localhost.localdomain (183.201.216.81.s-s.siw.siwnet.net [81.216.201.183]) by griffin.skarpodata.com (8.12.10/8.12.10) with ESMTP id i9CLCZ8c025719 for ; Tue, 12 Oct 2004 23:12:36 +0200 To: The development of GRUB 2 References: <6C8637B2-1C58-11D9-AD2F-000A95A0560C@penguinppc.org> <877jpvj0r9.fsf@night.trouble.net> <0224E79D-1C82-11D9-A7DE-000A95A0560C@penguinppc.org> From: Johan Rydberg Date: Tue, 12 Oct 2004 21:49:08 +0200 In-Reply-To: <0224E79D-1C82-11D9-A7DE-000A95A0560C@penguinppc.org> (Hollis Blanchard's message of "Tue, 12 Oct 2004 14:07:49 -0500") Message-ID: <87vfdfhg3v.fsf@night.trouble.net> User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: ChangeLogs? X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Oct 2004 21:56:32 -0000 Hollis Blanchard writes: > A worthy goal... though you don't need a ChangeLog file for that when > you have version control logs. Your "changeset comment" just goes in > the commit message. Commit messages are per-file, not per changeset. > Also, you can see that changeset comments on a project like the Linux > kernel are not nearly as verbose as the ChangeLog standards here. Linux uses BitKeeper, a commerical changeset based VC system. > Even CVS, which is not exactly a shining star of version control, can > accomplish this task very easily through either "cvs log " or > "cvs annotate ". The thing is that you want a greater context than just a single file. >> Remember that you should only describe _what_ you have changed. If >> you want to clearify something, put it in a comment in the source. > > But "new variable" and "new function" isn't even close to telling you > _what_ . I think it is. That is exactly what you have changed: you have added a new variable or function. If you want to describe the variable or function in greater detail, do so in the altered file (the source.) ~j