From: Fritz Jetzek <fritz.jetzek@i-dmedia.com>
To: guile-gtk@sourceware.cygnus.com
Cc: jalexstark@mindspring.com
Subject: Re: Looking for the Guile-Gtk tutorial...
Date: Fri, 08 Jun 2001 09:55:00 -0000 [thread overview]
Message-ID: <992022808.506.0.camel@saigon> (raw)
In-Reply-To: <990639098.430.0.camel@saigon>
On 23 May 2001 19:31:35 +0200, Fritz Jetzek wrote:
>> Hi,
>>
>> an earlier posting on this mailing list said the Guile/GTK tutorial
>> would be on http://www2.eng.cam.ac.uk/~jas/misc/gg-tutorial.tar.gz ,
>> however, the url is invalid as it seems. Is anyone around who could help
>> me out with a copy?
>>
>> Thanks a lot.
>>
>> Regards,
>> Fritz
>>
>> P.s. please CC - I'm not on the list.
>Fritz,
>Could you send a reply to your own message saying that the material can
be found at
> http://mdag.org/users/stark/software/description.html
>Also note that I distribute this `as is', and I haven't been able to
update them recently.
>Thanks,
>Alex.
Here we go. Thanks for the hint:)
Fritz
prev parent reply other threads:[~2001-06-08 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-23 9:34 Fritz Jetzek
2001-06-08 9:55 ` Fritz Jetzek [this message]
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=992022808.506.0.camel@saigon \
--to=fritz.jetzek@i-dmedia.com \
--cc=guile-gtk@sourceware.cygnus.com \
--cc=jalexstark@mindspring.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).