Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@codesourcery.com>
To: "Baars, M.J." <mjbaars1977.gdb@gmail.com>
Cc: gdb@sourceware.org, gdb-patches@sourceware.org,
	Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: Re: print_npx_status_word
Date: Sat, 16 Apr 2011 14:29:00 -0000	[thread overview]
Message-ID: <20110416142809.GA28255@caradoc.them.org> (raw)
In-Reply-To: <4DA99DA1.2090708@gmail.com>

On Sat, Apr 16, 2011 at 03:46:09PM +0200, Baars, M.J. wrote:
> On 04/16/2011 10:24 AM, Mark Kettenis wrote:
> >>Date: Sat, 16 Apr 2011 08:08:48 +0200
> >>From: "Baars, M.J."<mjbaars1977.gdb@gmail.com>
> >>
> >>Hi Tom,
> >>
> >>I believe this is the format you requested?
> >No!  This is a .tar.gz.  Proper diffs don't come as a .tar.gz.
> Oops... did I remove one of your entries in the ChangeLog? :)

If you want a patch to be committed, eventually you're going to have
to say why.  What's the goal of the patch?

Also, why on earth are you messing about with old changelog entries?

-- 
Daniel Jacobowitz
Mentor Graphics


  reply	other threads:[~2011-04-16 14:29 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                     ` Daniel Jacobowitz [this message]
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                         ` print_npx_status_word Eli Zaretskii
     [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=20110416142809.GA28255@caradoc.them.org \
    --to=dan@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gdb@sourceware.org \
    --cc=mark.kettenis@xs4all.nl \
    --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