Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: "David S. Miller" <davem@redhat.com>
Cc: thorpej@wasabisystems.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Sparc/Linux fixes part 1
Date: Sat, 20 Apr 2002 23:41:00 -0000	[thread overview]
Message-ID: <3CC25F13.1040108@cygnus.com> (raw)
In-Reply-To: <20020420.212348.61263564.davem@redhat.com>

>  From: Jason R Thorpe <thorpej@wasabisystems.com>
> Date: Sat, 20 Apr 2002 21:24:25 -0700
> 
>    On Sat, Apr 20, 2002 at 08:09:57PM -0700, David S. Miller wrote:
>    
>     > I produced a backlog of 12 patches, then Jason Thorpe posted his
>     > patch.  You choose to review his change before any of the rest of
>     > mine.
>    
>    Err, I don't think you're being completely fair to Andrew, here.  The
>    patch I posted to frame.c today was quite trivial, and the code it fixed
>    was pretty obviously broken, and thus the patch very easy to review.
> 
> I posted patches of similar complexity.  For example:
> 
> 	http://sources.redhat.com/ml/gdb-patches/2002-04/msg00675.html
> 

The number of lines in a patch is not a good indicator of the amount of 
time required or the relative priority of a submitted change.

The other patch didn't contain a single macro, it refered to one 
one-line function (which I know backwards), it fixes a core dump, and 
the patch itself contained all the relevant code in question.  Given I 
only just changed the code myself, I'm also ``on the hook'' for any fallout.

On the other hand, the above patch contains alloca, macros, and zero 
context (surounding code).  It is changing code that currently works 
(just not efficiently) and, if wrong, will cause a stack buffer overrun.

enjoy,Andrew


  reply	other threads:[~2002-04-21  6:41 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-19 14:54 David S. Miller
2002-04-19 18:37 ` Michael Snyder
2002-04-19 18:43   ` David S. Miller
2002-04-19 18:55   ` David S. Miller
2002-04-19 19:13     ` Andrew Cagney
2002-04-19 19:16       ` David S. Miller
2002-04-19 19:18       ` David S. Miller
2002-04-19 19:46         ` Andrew Cagney
2002-04-19 19:53           ` David S. Miller
2002-04-20 19:01             ` David S. Miller
2002-04-20 19:13               ` Jason R Thorpe
2002-04-20 19:44                 ` Andrew Cagney
2002-04-20 20:06               ` Andrew Cagney
2002-04-20 20:18                 ` David S. Miller
2002-04-20 21:24                   ` Jason R Thorpe
2002-04-20 21:32                     ` David S. Miller
2002-04-20 23:41                       ` Andrew Cagney [this message]
2002-04-22  9:24               ` Elena Zannoni
2002-04-22  3:55             ` Richard Earnshaw
2002-04-22  4:09               ` David S. Miller
2002-04-19 19:55           ` David S. Miller
2002-04-20 10:00     ` Jason R Thorpe
2002-04-20 17:59       ` David S. Miller
2002-04-20 19:04         ` Jason R Thorpe
2002-04-20 19:19           ` David S. Miller
2002-04-20 19:24             ` Jason R Thorpe
2002-04-20 19:26               ` David S. Miller
2002-04-20 20:32               ` [RFA] Sparc OS abi gdbarch init (was Re: [RFA] Sparc/Linux fixes part 1) David S. Miller

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=3CC25F13.1040108@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=davem@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=thorpej@wasabisystems.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