This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [non-stop] 01/10 Add "executing" property


> Date: Sun, 15 Jun 2008 21:26:17 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
> 
> On Mon, Jun 16, 2008 at 12:47:43AM +0300, Eli Zaretskii wrote:
> > > 	* Makefile.in (event-top.o, frame.o, inf-loop.o, top.o):
> > > 	Update.
> > 
> > I think you should tell what prerequisites were added to each target.
> > A simple "update" will never reveal when a prerequisite was added, if
> > someone will ever want to know.
> 
> I don't think it's necessary to duplicate the contents of the patch in
> the changelog.

How else would one know when a certain change was done to a certain
file?  For that matter, why do we bother writing log entries at all?

> Do you really think it's useful?  We've never asked to
> do this (see the cvs log of Makefile.in for plenty of examples), and I
> would resist; changelogs already take a long time to write.

It's common practice in GNU projects.  I'm quite shocked to learn that
some of us resist it.  Yes, our log entries are already quite sloppy
and unhelpful, but there are limits.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]