From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9579 invoked by alias); 18 Mar 2009 15:46:50 -0000 Received: (qmail 9568 invoked by uid 22791); 18 Mar 2009 15:46:46 -0000 X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,J_CHICKENPOX_82,SPF_PASS X-Spam-Check-By: sourceware.org Received: from fencepost.gnu.org (HELO fencepost.gnu.org) (140.186.70.10) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 18 Mar 2009 15:46:35 +0000 Received: from ams by fencepost.gnu.org with local (Exim 4.67) (envelope-from ) id 1LjxyR-0002PV-L5; Wed, 18 Mar 2009 11:46:31 -0400 To: Eli Zaretskii CC: drow@false.org, nathan@codesourcery.com, gdb-patches@sourceware.org In-reply-to: (message from Eli Zaretskii on Tue, 17 Mar 2009 21:41:02 +0200) Subject: Re: more missing gplv3 notices References: <49BE06F6.3090008@codesourcery.com> <49BF5977.2020803@codesourcery.com> <20090317191251.GA24913@caradoc.them.org> Message-Id: From: "Alfred M. Szmidt" Date: Wed, 18 Mar 2009 16:01:00 -0000 X-IsSubscribed: yes 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 X-SW-Source: 2009-03/txt/msg00382.txt.bz2 > > 2009-01-12 Christopher Faylor > > > > * amd64-windows-nat.c Rename gdb-specific win32_* to windows_* > > throughout. > > * i386-cygwin-tdep.c: Ditto. > > * i386-windows-nat.c: Ditto. > > * windows-nat.h: Ditto. > > * windows-tdep.c: Ditto. > > * windows-tdep.h: Ditto. > > * windows-nat.c: Ditto. > > > > See the node "Style of Change Logs" in standards.info for details. > > It does not say that explicitly (doesn't mention multi-file changes at > all), and this is not the prevailing style used by GDB developers > based on my survey of the changelogs. Sorry, I forgot I shouldn't talk about these things. Though, to open a can of worms, | It's important to name the changed function or variable in full. | Don't abbreviate function or variable names, and don't combine them. | Subsequent maintainers will often search for a function name to find all | the change log entries that pertain to it; if you abbreviate the name, | they won't find it when they search. | | For example, some people are tempted to abbreviate groups of function | names by writing `* register.el ({insert,jump-to}-register)'; this is | not a good idea, since searching for `jump-to-register' or | `insert-register' would not find that entry.