From: Keith Seitz <keiths@cygnus.com>
To: Fernando Nasser <fnasser@redhat.com>
Cc: "Martin M. Hunt" <hunt@redhat.com>,
Insight Mailing List <insight@sources.redhat.com>
Subject: Re: [RFA] memory window patch
Date: Thu, 15 Nov 2001 11:43:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.33.0111151139520.3592-100000@makita.cygnus.com> (raw)
Message-ID: <20011115114300.MFEd4y_C11G1UC2wtf4lxBsrtG6ReoX-BpQaWLhSr-0@z> (raw)
In-Reply-To: <3BEC0D01.717F7465@redhat.com>
On Fri, 9 Nov 2001, Fernando Nasser wrote:
> Thank you so much Martin!
Indeed!
> Lets just see if your patch does not conflict with Keith's clean-ups
> before
> checking it in.
Which cleanups? The big cleanups that are on my list of hot-spots is
conversion to more events and ui_out. And that whole tix->blt thing.
I don't think that this patch would interfere with any of that, though.
(Martin) If you've tested with linux and a cross or two and it all works,
then by all means, check it in.
Keith
next prev parent reply other threads:[~2001-11-15 11:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-08 17:12 Martin M. Hunt
2001-11-09 9:06 ` Fernando Nasser
2001-10-02 12:23 ` Keith Seitz [this message]
2001-11-15 11:43 ` Keith Seitz
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=Pine.GSO.4.33.0111151139520.3592-100000@makita.cygnus.com \
--to=keiths@cygnus.com \
--cc=fnasser@redhat.com \
--cc=hunt@redhat.com \
--cc=insight@sources.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).