From: Joel Brobecker <brobecker@adacore.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] New inf-procfs module (replacing procfs)
Date: Sat, 14 Jan 2006 03:33:00 -0000 [thread overview]
Message-ID: <20060114033315.GL10275@adacore.com> (raw)
In-Reply-To: <200601132027.k0DKRvSf021579@elgar.sibelius.xs4all.nl>
Hi Mark,
> It'd be great if you would be willing to do the cleanup. If not,
> could you give me two weeks to finish my (barely started) attempt to
> do it?
I think I can, if you tell me what you'd like to be done. Unfortunately,
I am about to take a few days off sometimes soon (it will be the end
of next week), and I will then be traveling so won't have time for it
before the end of January.
It's up to you: If you'd like to do it, then please do, my traveling
in effect gives you the two weeks. Otherwise, you can leave it to me.
I'm a bit concerned that I have a track record to forget things and
never pick them up for a long time when I am forced to leave them....
(work pressure). You don't have to, but you can nag me.
BTW: You didn't tell me whether I was on the right track or not...
target-vector handling is something relatively new to me, believe
it or not, so I had to study it a bit.
Would you also recommend one thread-support code that follows
the current standards? I agree that sol-threads could use a good
cleanup, and I am interested in doing it. I think we should be
able to get rid of things like:
extern int procfs_suppress_run;
at the very least.
Thanks,
--
Joel
next prev parent reply other threads:[~2006-01-14 3:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 17:40 Joel Brobecker
2006-01-13 20:28 ` Mark Kettenis
2006-01-14 3:33 ` Joel Brobecker [this message]
2006-01-27 20:10 ` Michael Snyder
2006-01-27 20:33 ` Joel Brobecker
2006-01-27 21:46 ` 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=20060114033315.GL10275@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
/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