Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Vladimir Prus <ghost@cs.msu.su>, gdb-patches@sources.redhat.com
Subject: Re: [5/9] Associate parsed condition with location
Date: Sat, 08 Sep 2007 13:46:00 -0000	[thread overview]
Message-ID: <20070908134613.GA27737@caradoc.them.org> (raw)
In-Reply-To: <usl5pqrlp.fsf@gnu.org>

On Sat, Sep 08, 2007 at 03:17:06PM +0300, Eli Zaretskii wrote:
> We only need the function names, that's all.  A year from now, someone
> who will want to find out when this change was done in one of those
> functions, will grep the ChangeLog's for the function's name.

I don't think this is necessary, and it's definitely not customary.
Here's two of the examples from the GNU Coding Standards.  Re "Likewise":

* register.el (insert-register): Return nil.
(jump-to-register): Likewise.


And for large mechanical changes:

When you change the calling sequence of a function in a simple fashion,
and you change all the callers of the function to use the new calling
sequence, there is no need to make individual entries for all the
callers that you changed.  Just write in the entry for the function
being called, ``All callers changed''---like this:

@example
* keyboard.c (Fcommand_execute): New arg SPECIAL.
All callers changed.
@end example


-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-09-08 13:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-07 20:42 Vladimir Prus
2007-09-08 11:12 ` Eli Zaretskii
2007-09-08 11:27   ` Vladimir Prus
2007-09-08 12:17     ` Eli Zaretskii
2007-09-08 13:46       ` Daniel Jacobowitz [this message]
2007-09-08 16:17         ` Eli Zaretskii
2007-09-08 16:50           ` Daniel Jacobowitz
2007-09-22 17:53   ` Vladimir Prus
2007-09-22 18:33     ` Eli Zaretskii
2007-09-22 18:43       ` 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=20070908134613.GA27737@caradoc.them.org \
    --to=drow@false.org \
    --cc=eliz@gnu.org \
    --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