Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@codesourcery.com>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Cleanup pending breakpoints floatsam
Date: Thu, 08 Nov 2007 18:11:00 -0000	[thread overview]
Message-ID: <m3hcjwppz0.fsf@codesourcery.com> (raw)
In-Reply-To: <fgveep$t2$1@ger.gmane.org> (Vladimir Prus's message of "Thu, 08 Nov 2007 19:44:46 +0300")


Vladimir Prus <ghost at cs.msu.su> writes:
> Jim Blandy wrote:
>
>> 
>> Vladimir Prus <ghost at cs.msu.su> writes:
>>> After pending breakpoints were changed for better, a number of
>>> functions have 'pending_bp' parameter that is not used in any
>>> way. This patch removes it. OK?
>>>
>>> (I'll write ChangeLog entry if this patch is approved)
>> 
>> Looks good to me; please commit.
>
> Thanks. The final patch with changelog is attached.
>  
>> (This patch was mechanical and touched a number of functions, so I can
>> understand why you'd rather put off writing the ChangeLog entry for
>> it.  But in general, a patch should be posted with a ChangeLog entry:
>> it helps reviewers understand the patch, and of course the entry is
>> subject to review itself.)
>
> It's this a bit too pedantic, for this case? This is as mechanical patch
> as it can get, so ChangeLog won't have much value in understanding the patch.

What I meant was, in this case it's not a problem, for just the reason
you say.  But in general, patches should include ChangeLog entries
when posted for review.


  reply	other threads:[~2007-11-08 18:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-08  8:56 Vladimir Prus
2007-11-08 16:14 ` Jim Blandy
2007-11-08 16:47   ` Vladimir Prus
2007-11-08 18:11     ` Jim Blandy [this message]
2007-11-08 18:36       ` 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=m3hcjwppz0.fsf@codesourcery.com \
    --to=jimb@codesourcery.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    /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