From: Mark Wielaard <mark@klomp.org>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: frysk@sourceware.org
Subject: Re: frysk-core/frysk/proc ChangeLog IsaIA32.java I ...
Date: Wed, 27 Jun 2007 17:35:00 -0000 [thread overview]
Message-ID: <1182964334.3636.25.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <46827A9D.70300@redhat.com>
Hi Phil,
On Wed, 2007-06-27 at 09:56 -0500, Phil Muldoon wrote:
> 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..
Yes I think you hit the actual issue. I agree.
And I think that was why I was so disappointed about the process. A
design discussion is good and I thought that was what we were having.
But all we got in the end was an imho random renaming of a perfectly
good package name without any real design discussion. Cleaning up after
such a change isn't that hard and that was indeed not what I was angry
about. Although of course I rather not see extra work in the first
place. I would have happily done that work if I got the feeling there
was a real cleaned up design coming that couldn't be done without such a
renaming of packages. But that didn't emerge from the discussion at all.
And you are right that was what the discussion should have been about.
Cheers,
Mark
next prev parent reply other threads:[~2007-06-27 17:12 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
2007-06-27 17:35 ` Mark Wielaard [this message]
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=1182964334.3636.25.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--cc=frysk@sourceware.org \
--cc=pmuldoon@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).