Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@redhat.com>
To: "David S. Miller" <davem@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Improve Sparc epilogue analysis
Date: Thu, 25 Apr 2002 14:16:00 -0000	[thread overview]
Message-ID: <3CC86F55.CA45E27B@redhat.com> (raw)
In-Reply-To: <20020424.180531.51276912.davem@redhat.com>

"David S. Miller" wrote:
> 
>    From: Michael Snyder <msnyder@redhat.com>
>    Date: Wed, 24 Apr 2002 17:36:02 -0700
> 
>    The parts that are NOT mentioned in the changelog (your changes
>    to the logic in sparc_init_extra_frame_info) are not OK, first
>    because you didn't mention them in the changelog, and second
>    because I can't convince myself that they are right.
> 
> Michael, I hate keeping on about this, but I did mention
> them in my changes:
> 
>         (sparc_init_extra_frame_info): Use sparc_skip_prologue to find
>         prologue bounds instead of looking at line number info by hand.

That entry says nothing about changing the logic or the functional
behavior.

> I know you're going to explode at me, 

Why would you say that?  Have I exploded at you up till now?

> but you seem to make a lot of errors reviewing my changes. 

If so, I would like to know about it.  Please detail 
one of my errors for the group.

> Please settle down, take your time. 

I'm going to remind you of this comment the next time you
rail about my not reviewing one of your changes on a Saturday.

> At
> this point I'd much rather you delay than review things haphazardly.

And I'd much rather you consider my reviews seriously, rather
than assume they are haphazard or erroneous.  I have been doing
this for a while, you know...

Your change to sparc_init_extra_frame_info changes its logic
and its black-box behavior.  You have said nothing about why
you made this change.  It's not my job to guess why you did it, 
it's my job to reject your change until you explain it.

It's also not my job to take shit from you.  Change your attitude, 
David.  Change it now.


  parent reply	other threads:[~2002-04-25 21:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-20  0:31 David S. Miller
2002-04-23 12:32 ` Michael Snyder
2002-04-24  0:09   ` David S. Miller
2002-04-24 16:27     ` Michael Snyder
2002-04-24 17:15       ` David S. Miller
2002-04-24 17:48         ` Michael Snyder
2002-04-24 17:54           ` David S. Miller
2002-04-24 18:02           ` David S. Miller
2002-04-25 14:11             ` Michael Snyder
2002-04-25 18:33               ` David S. Miller
2002-04-24 18:15           ` David S. Miller
2002-04-24 22:10             ` Eli Zaretskii
2002-04-25 11:44               ` Michael Snyder
2002-04-25 14:16             ` Michael Snyder [this message]
2002-04-25 18:38               ` David S. Miller
2002-04-24 19:10           ` David S. Miller
2002-04-25 14:25             ` 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=3CC86F55.CA45E27B@redhat.com \
    --to=msnyder@redhat.com \
    --cc=davem@redhat.com \
    --cc=gdb-patches@sources.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