From: Phil Muldoon <pmuldoon@redhat.com>
To: Andrew Cagney <cagney@redhat.com>
Cc: Mark Wielaard <mark@klomp.org>,
frysk@sourceware.org, cagney@sourceware.org
Subject: Re: frysk-core/frysk/proc ChangeLog IsaIA32.java I ...
Date: Wed, 27 Jun 2007 17:08:00 -0000 [thread overview]
Message-ID: <46827A9D.70300@redhat.com> (raw)
In-Reply-To: <468266E7.70707@redhat.com>
Andrew Cagney wrote:
> Mark,
>
> These changes affect three people directly: me, you and phil. Phil
> and I want this; and for you, it is cosmetic. Why are you so resistant
> to what you yourself recognize has no effect on the code you work on?
I've been caught up in deliverables so I have not been really paying
attention to this thread, perhaps as much as I should have. Apologies
for that. I think there are several issues caught up here, and they are
getting confused as one.
First I do not care about what the name is. It's not important to me.
dead and live, proc and corefile, pink or blue, vanilla or strawberry it
is something that is fluid and can change now and in the future. That
can be taken as complicit agreement of disagreement. I just don't have
strong feelings here.
However, I think the larger picture here, and I think is lost in the
"change over discussion" trend, is that the current proc model is pretty
faulty in some of its assumptions and really needs refactoring. For the
last six months I've been working on tweaking this and that so that
Proc/Task/Host is not live process specific. So in the longer to mid
term there really needs to be a rethink of that model.. Right now,
Andrew, Mark and myself are the main people twiddling the bits here, I
think we all have our own strong ideas on how this should work. I think
this thread has spawned because these ideas are not reconciled. In the
debate of this thread, and myself just ignoring it for various reasons,
I think there is a plain and clear need for a roundtable I'd hazard a
guess we agree more than we disagree, and it just needs to be thrashed
out. However we all have our deadlines, and for one reason or another
this design discussion has slipped through the cracks, and people have
moved forward with their ideas. I'm also guilty of not discussing a lot
of my changes.
We should table a discussion on the whys and the why nots soon.
Regards
Phil
next prev parent reply other threads:[~2007-06-27 14:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070626221253.13799.qmail@sourceware.org>
2007-06-27 13:32 ` Mark Wielaard
2007-06-27 14:56 ` Andrew Cagney
2007-06-27 17:08 ` Phil Muldoon [this message]
2007-06-27 17:35 ` Mark Wielaard
2007-06-28 10:23 ` Phil Muldoon
2007-07-06 21:43 ` Andrew Cagney
2007-06-27 17:12 ` Mark Wielaard
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=46827A9D.70300@redhat.com \
--to=pmuldoon@redhat.com \
--cc=cagney@redhat.com \
--cc=cagney@sourceware.org \
--cc=frysk@sourceware.org \
--cc=mark@klomp.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).