From: Mike Gran <spk121@yahoo.com>
To: David Pirotte <david@altosw.be>
Cc: Guile User <guile-user@gnu.org>
Subject: g-golf status
Date: Wed, 19 Jun 2019 15:35:37 -0700 [thread overview]
Message-ID: <20190619223537.GA11756@spikycactus.attlocal.net> (raw)
In-Reply-To: <20180114100046.5f321895@capac>
Hi David,
I notice you've been making some commits on g-golf. How's the state of the
project?
I've been playing with GObject from the other (guile-gi) codebase, and
it is a bit of a nightmare. Through brute force, it is beginning to
work, but, there is no methodology behind the work. It is all
spaghetti.
-Mike Gran
next prev parent reply other threads:[~2019-06-19 22:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-14 10:03 g-golf Catonano
2018-01-14 10:08 ` g-golf Amirouche Boubekki
2018-01-14 10:46 ` g-golf Catonano
2018-01-14 12:00 ` g-golf David Pirotte
2018-01-14 12:17 ` g-golf Catonano
2018-01-14 12:35 ` g-golf Catonano
2018-01-14 13:09 ` g-golf Catonano
2018-01-14 13:10 ` g-golf David Pirotte
2018-01-14 13:32 ` g-golf Catonano
2019-06-19 22:35 ` Mike Gran [this message]
2019-06-21 4:05 ` g-golf status David Pirotte
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190619223537.GA11756@spikycactus.attlocal.net \
--to=spk121@yahoo.com \
--cc=david@altosw.be \
--cc=guile-user@gnu.org \
/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).