Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Paul Koning <pkoning@equallogic.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: proposed PATCH: make watchpoints work correctly
Date: Wed, 28 May 2003 16:42:00 -0000	[thread overview]
Message-ID: <20030528164219.GA3397@nevyn.them.org> (raw)
In-Reply-To: <16084.56661.295275.544414@pkoning.dev.equallogic.com>

On Wed, May 28, 2003 at 12:01:25PM -0400, Paul Koning wrote:
> I have copyright assignment papers on file with FSF for gcc and
> binutils -- does that cover this or should I add paperwork for gdb
> specifically?   Also, I have no write access to anything.  Lastly, I'm
> not sure how many things have to be tested for a patch to be
> considered acceptable.  

You'll need separate copyright papers for GDB; sorry, I was under the
impression you already had them.

As for the patch itself, I just skimmed it, but using a global in
handle_inferior_event and in remote.c is not kosher.  We're trying to
cut back on the mess in infrun, not increase it.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  parent reply	other threads:[~2003-05-28 16:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28 16:01 Paul Koning
2003-05-28 16:02 ` Paul Koning
2003-05-28 16:42 ` Daniel Jacobowitz [this message]
2003-05-28 19:54 ` Eli Zaretskii
2003-05-28 20:27   ` Paul Koning
2003-05-29  3:27     ` Eli Zaretskii
2003-05-29  4:36       ` Nathan J. Williams
2003-05-29 15:14         ` Eli Zaretskii
2003-05-29 15:17       ` Paul Koning
2003-05-29 15:37         ` Daniel Jacobowitz
2003-05-29 17:41           ` Paul Koning
2003-06-02  4:19         ` Eli Zaretskii
2003-06-04 14:51           ` Paul Koning
2003-06-29  4:15             ` Daniel Jacobowitz

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=20030528164219.GA3397@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=pkoning@equallogic.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