public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Andrew Cagney <cagney@redhat.com>
Cc: frysk@sourceware.org
Subject: Re: putting Ptrace back to 64-bit
Date: Thu, 02 Aug 2007 14:00:00 -0000	[thread overview]
Message-ID: <1186063226.15044.76.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <46B1D016.909@redhat.com>

Hi Andrew,

On Thu, 2007-08-02 at 08:37 -0400, Andrew Cagney wrote:
> Mark Wielaard wrote:
> > On Wed, 2007-08-01 at 22:58 -0400, Andrew Cagney wrote:
> >> I don't understand the rationale behind this change:
> >
> > It was proposed and explained as a follow up for the LogicalMemoryBuffer
> > under "A couple of things to note, questions and upcoming work" at:
> > http://sourceware.org/ml/frysk/2007-q3/msg00163.html
> > And the rationale was again added when the actual patch to implement it
> > was posted: http://sourceware.org/ml/frysk/2007-q3/msg00216.html   
> 
> Please run such things directly past me.

I am happy for people to review my patches before committing. But you
have to give me some guidance here since till now we didn't have any
formal reviews, but were relying on unit tests to catch any badness. In
this case I thought it was a simple cleanup refactoring to make the real
work that I was doing easier and the code safer (as explained in that
first email). What kind of changes do you want to have reviewed first
and by who. Do you want people to be CCed on such patches? Can't we just
make it so that if a patch is posted to the list anybody can review it
to make sure it is sane?

Cheers,

Mark

      reply	other threads:[~2007-08-02 14:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-02  2:58 Andrew Cagney
2007-08-02  8:40 ` Mark Wielaard
2007-08-02 12:37   ` Andrew Cagney
2007-08-02 14:00     ` Mark Wielaard [this message]

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=1186063226.15044.76.camel@dijkstra.wildebeest.org \
    --to=mark@klomp.org \
    --cc=cagney@redhat.com \
    --cc=frysk@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).