From: Rob Browning <rlb@cs.utexas.edu>
To: Ariel Rios <ariel@linuxppc.org>
Cc: guile-gtk@sourceware.cygnus.com
Subject: Re: Time to talk about g-wrap
Date: Sat, 14 Apr 2001 16:23:00 -0000 [thread overview]
Message-ID: <87k84n2hhj.fsf@raven.localnet> (raw)
In-Reply-To: <987217943.9980.0.camel@soleil>
Ariel Rios <ariel@linuxppc.org> writes:
> I think it is time to think about using gwrap inside gnome-guile So
> can we restart the discussion on that?
OK. I'm wondering what the best way to proceed would be. Presuming
it would be helpful for you to have an idea of where g-wrap now
stands, we could start with a description of that. I've needed to
write some documentation for the new implementation for a while
anyhow, and now's as good a time as any.
After that, we could discuss where g-wrap fails to be suitable for
gnome guile and see how we might fix that.
Or would you prefer to handle things some other way?
--
Rob Browning <rlb@cs.utexas.edu> PGP=E80E0D04F521A094 532B97F5D64E3930
next parent reply other threads:[~2001-04-14 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <987217943.9980.0.camel@soleil>
2001-04-14 16:23 ` Rob Browning [this message]
[not found] ` <987293844.14903.3.camel@soleil>
2001-04-14 20:23 ` Rob Browning
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=87k84n2hhj.fsf@raven.localnet \
--to=rlb@cs.utexas.edu \
--cc=ariel@linuxppc.org \
--cc=guile-gtk@sourceware.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).