From: Ian Roxborough <irox@redhat.com>
To: Keith Seitz <keiths@cygnus.com>
Cc: "Martin M. Hunt" <hunt@redhat.com>,
Insight Maling List <insight@sources.redhat.com>
Subject: Re: [PATCH/hack] Running from build dir again
Date: Thu, 20 Sep 2001 11:28:00 -0000 [thread overview]
Message-ID: <3BAA381D.450E5D3@redhat.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0109201058520.20326-100000@makita.cygnus.com>
Keith Seitz wrote:
> We should either not use them, or submit patches to make them more useful.
> (The scrolledwindow thingy is worthless, and I don't think it is fixable.)
I think we would get more value per hack if we concentrate on BLT, which
seems to be able to replace almost all of the tix and IWidget functionality
we use.
The added bonus of reducing the overall number of tool kits we need is
also appealing for me.
Ian.
next prev parent reply other threads:[~2001-09-20 11:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-19 11:09 Keith Seitz
2001-09-19 12:03 ` Ian Roxborough
2001-09-19 12:08 ` Keith Seitz
2001-09-19 12:28 ` Ian Roxborough
2001-09-20 10:57 ` Martin M. Hunt
2001-09-20 11:01 ` Keith Seitz
2001-09-20 11:28 ` Ian Roxborough [this message]
2001-09-20 11:31 ` 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=3BAA381D.450E5D3@redhat.com \
--to=irox@redhat.com \
--cc=hunt@redhat.com \
--cc=insight@sources.redhat.com \
--cc=keiths@cygnus.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).