This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch-readline] history file reading
- From: "Brian J. Fox" <bfox at ai dot mit dot edu>
- To: Daniel Jacobowitz <drow at false dot org>, Denis PILAT <denis dot pilat at st dot com>, Chet Ramey <chet dot ramey at case dot edu>
- Cc: Eli Zaretskii <eliz at gnu dot org>, <gdb-patches at sources dot redhat dot com>, <bash-maintainers at gnu dot org>
- Date: Tue, 21 Mar 2006 08:29:20 -0800
- Subject: Re: [patch-readline] history file reading
> From: Daniel Jacobowitz <drow@false.org>
> Date: Tue, 21 Mar 2006 09:58:42 -0500
> To: Denis PILAT <denis.pilat@st.com>, Chet Ramey <chet.ramey@case.edu>
> Cc: Eli Zaretskii <eliz@gnu.org>, <gdb-patches@sources.redhat.com>,
> <bash-maintainers@gnu.org>
> Subject: Re: [patch-readline] history file reading
>
> Our ChangeLog entries have two spaces between date and name, and two
> between name and date. The indented portion starts with a tab on every
> line. The first character should usually be capitalized. Also, they
> cover only "what" and not "why".
Since when do ChangeLog entries not say "why"? Without this information, it
is impossible to tell if the change needs to stay or not in the future.
I've certainly always included "why" in my ChangeLog entries.
Is this a personal preference, or are you quoting a new GNU mantra?
Thanks,
Brian