Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [non-stop] 01/10 Add "executing" property
Date: Mon, 16 Jun 2008 07:22:00 -0000	[thread overview]
Message-ID: <g35201$2uf$2@ger.gmane.org> (raw)
In-Reply-To: <20080616012617.GA8944@caradoc.them.org>

Daniel Jacobowitz wrote:

> 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.  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 actually fairly weird that one has to maintain dependencies by hand,
I don't think I know any single project still alive that needs that. And
duplicating that dependency information in ChangeLog entries will make
a painful thing twice as painful. Not that the question "who added this
dependency" seems like a common question to ask.

- Volodya



  parent reply	other threads:[~2008-06-16  6:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-15 21:04 Pedro Alves
2008-06-15 22:18 ` Eli Zaretskii
2008-06-16  1:42   ` Daniel Jacobowitz
2008-06-16  3:23     ` Eli Zaretskii
2008-06-16  6:45       ` ChangeLog entries [was Re: [non-stop] 01/10 Add "executing" property] Nick Roberts
2008-06-16  7:22     ` Vladimir Prus [this message]
2008-06-17  0:40       ` [non-stop] 01/10 Add "executing" property Eli Zaretskii
2008-06-17 17:10         ` Vladimir Prus
2008-06-17 20:38           ` Eli Zaretskii
2008-06-23 17:27       ` Tom Tromey
2008-06-17 16:14   ` Joel Brobecker
2008-06-17 18:24     ` Eli Zaretskii
2008-06-17 18:32       ` Joel Brobecker
2008-06-18  0:22         ` Eli Zaretskii
2008-06-17 18:34       ` Pedro Alves
2008-06-17 20:58         ` Eli Zaretskii
2008-06-23  1:13         ` Daniel Jacobowitz
2008-06-23 11:54           ` Vladimir Prus
2008-06-23 14:41             ` Pedro Alves
2008-06-23 18:22               ` Eli Zaretskii
2008-06-23 18:25                 ` Vladimir Prus
2008-06-23 19:52                   ` Pedro Alves
2008-06-24  1:13                     ` Eli Zaretskii
2008-06-23 18:14             ` Eli Zaretskii
2008-07-02  3:29           ` Pedro Alves
2008-06-25 19:02 ` Vladimir Prus
2008-06-25 19:13   ` Pedro Alves
2008-06-25 19:22     ` Daniel Jacobowitz
2008-06-26 13:37       ` Vladimir Prus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='g35201$2uf$2@ger.gmane.org' \
    --to=vladimir@codesourcery.com \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox