This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch-readline] history file reading
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Andreas Schwab <schwab at suse dot de>
- Cc: bfox at ai dot mit dot edu, gdb-patches at sources dot redhat dot com, bash-maintainers at gnu dot org
- Date: Tue, 21 Mar 2006 22:02:10 +0200
- Subject: Re: [patch-readline] history file reading
- References: <C04569E0.30716%bfox@ai.mit.edu> <je7j6nhhk2.fsf@sykes.suse.de>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Andreas Schwab <schwab@suse.de>
> Cc: Daniel Jacobowitz <drow@false.org>,
> Denis PILAT <denis.pilat@st.com>, Chet Ramey <chet.ramey@case.edu>,
> Eli Zaretskii <eliz@gnu.org>, <gdb-patches@sources.redhat.com>,
> <bash-maintainers@gnu.org>
> Date: Tue, 21 Mar 2006 17:46:21 +0100
>
> "Brian J. Fox" <bfox@ai.mit.edu> writes:
>
> > Since when do ChangeLog entries not say "why"?
>
> http://www.gnu.org/prep/standards/html_node/Change-Log-Concepts.html#Change-Log-Concepts
>
> > Without this information, it is impossible to tell if the change needs
> > to stay or not in the future.
>
> "Why" should be written in a comment in the code, because that's where you
> are looking at if you wonder why something is done this way.
Right.