From: Ariel Rios <ariel@gnu.org>
To: rm@fabula.de
Cc: guile-gtk@sourceware.cygnus.com, guile-user@gnu.org
Subject: Re: gnome-guile-0.21pre4
Date: Sat, 05 Jan 2002 12:03:00 -0000 [thread overview]
Message-ID: <1010257411.695.3.camel@soleil> (raw)
In-Reply-To: <20020105113841.GA26171@www>
On Sat, 2002-01-05 at 06:38, rm@fabula.de wrote:
> Proxy request sent, awaiting response... 503 Service Unavailable
> 12:25:12 ERROR 503: Service Unavailable.
MMM It is working fine for me...
>
> > Any contributions to the defs files would be apreciated.
>
>
> What is needed? Aren't the .defs autogenerated?
defs files are used to autogenerate glue code.
I really don't have time to look what we are missing...
I am directing work towards Gtk 2.0
ariel
next prev parent reply other threads:[~2002-01-05 20:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 11:15 gnome-guile-0.21pre4 Ariel Rios
2002-01-05 3:30 ` gnome-guile-0.21pre4 rm
2002-01-05 12:03 ` Ariel Rios [this message]
2002-01-07 13:27 ` gnome-guile-0.21pre4 Neil Jerram
2002-01-07 17:57 ` gnome-guile-0.21pre4 rm
2002-01-07 14:04 ` gnome-guile-0.21pre4 Bo Forslund
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=1010257411.695.3.camel@soleil \
--to=ariel@gnu.org \
--cc=guile-gtk@sourceware.cygnus.com \
--cc=guile-user@gnu.org \
--cc=rm@fabula.de \
/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).