Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Newman, Mark (N-Superior Technical Resource Inc)" <mark.newman@lmco.com>
To: Andrew Cagney <ac131313@redhat.com>, Michael Snyder <msnyder@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: RE: FW: bug ????
Date: Thu, 21 Aug 2003 15:40:00 -0000	[thread overview]
Message-ID: <F56FBA314E8E5A41895F0DA8F6716A6D02A421@EMSS04M11.us.lmco.com> (raw)

I have no problem with either way.  My role was not of much significance
in this patch.

I have not received any assignment paperwork.

                                        Mark  

-----Original Message-----
From: Andrew Cagney [mailto:ac131313@redhat.com]
Sent: Thursday, August 21, 2003 11:28 AM
To: Michael Snyder
Cc: Newman, Mark (N-Superior Technical Resource Inc);
gdb-patches@sources.redhat.com
Subject: Re: FW: bug ????


> 2003-08-15  Mark Newman  <mark.newman@lmco.com>
> 
>        * tracepoint.c (trace_dump_command): Trace break address
>        is subject to DECR_PC_AFTER_BREAK.

Michael,

I'd use a change log like:

	YYYY-MM-DD Michael Snyder ...

		* tracepoint.c (..): ...
		Problem reported by Mark Newman.

so that it more exactly reflects the fact that you, and not Mark, made 
the change (while still giving due credit) (this makes auditing much 
much easier).

I've sent Mark the relevant paper work for an assignment (but that isn't

needed here).

Andrew



             reply	other threads:[~2003-08-21 15:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-21 15:40 Newman, Mark (N-Superior Technical Resource Inc) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-15 16:55 Newman, Mark (N-Superior Technical Resource Inc)
2003-08-15 18:21 ` Michael Snyder
2003-08-21 15:28   ` Andrew Cagney
2003-08-21 18:10     ` Michael Snyder

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=F56FBA314E8E5A41895F0DA8F6716A6D02A421@EMSS04M11.us.lmco.com \
    --to=mark.newman@lmco.com \
    --cc=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=msnyder@redhat.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