Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Baars, M.J." <mjbaars1977.gdb@gmail.com>
Cc: dan@codesourcery.com, gdb-patches@sourceware.org, gdb@sourceware.org
Subject: Re: print_npx_status_word
Date: Sat, 16 Apr 2011 16:45:00 -0000	[thread overview]
Message-ID: <8362qep2l9.fsf@gnu.org> (raw)
In-Reply-To: <4DA9C1FC.8040600@gmail.com>

> Date: Sat, 16 Apr 2011 18:21:16 +0200
> From: "Baars, M.J." <mjbaars1977.gdb@gmail.com>
> 
> > Also, why on earth are you messing about with old changelog entries?
> >
> The old function can thus be seen as obsolete, and should be removed 
> from the old log entries.

ChangeLog files are the record of GDB history.  We don't rewrite
history when we replace functions by better ones.  So please leave the
old log entries alone, and just add new ones.


  parent reply	other threads:[~2011-04-16 16:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4DA7166F.10302@gmail.com>
     [not found] ` <m3aafshl6l.fsf@fleche.redhat.com>
     [not found]   ` <4DA7ED79.3000400@gmail.com>
     [not found]     ` <m3ei53efd8.fsf@fleche.redhat.com>
     [not found]       ` <4DA87235.7060003@gmail.com>
     [not found]         ` <m3pqoncw78.fsf@fleche.redhat.com>
     [not found]           ` <4DA87479.50203@gmail.com>
     [not found]             ` <m3lizbcvt7.fsf@fleche.redhat.com>
2011-04-16  6:09               ` print_npx_status_word Baars, M.J.
2011-04-16  8:24                 ` print_npx_status_word Mark Kettenis
2011-04-16 13:46                   ` print_npx_status_word Baars, M.J.
2011-04-16 14:29                     ` print_npx_status_word Daniel Jacobowitz
2011-04-16 16:21                       ` print_npx_status_word Baars, M.J.
2011-04-16 16:33                         ` print_npx_status_word Mark Kettenis
2011-04-16 16:47                           ` print_npx_status_word Baars, M.J.
2011-04-16 17:10                             ` print_npx_status_word Mark Kettenis
2011-04-16 17:55                               ` print_npx_status_word Baars, M.J.
2011-04-16 18:07                                 ` print_npx_status_word Marek Polacek
2011-04-18 17:00                               ` print_npx_status_word Tom Tromey
2011-04-16 16:45                         ` Eli Zaretskii [this message]
     [not found]                   ` <4DA99DA1.2090708__5871.13250880993$1302961604$gmane$org@gmail.com>
2011-04-18 17:04                     ` print_npx_status_word Tom Tromey
2011-04-19 19:01                       ` print_npx_status_word Baars, M.J.
2011-04-19 19:53                         ` print_npx_status_word Pedro Alves
2011-04-19 20:11                         ` print_npx_status_word Tom Tromey
2011-04-18 17:04                 ` print_npx_status_word Tom Tromey
2011-04-14 16:17 print_npx_status_word Baars, M.J.

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=8362qep2l9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dan@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gdb@sourceware.org \
    --cc=mjbaars1977.gdb@gmail.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