From: Andy Wingo <wingo@pobox.com>
To: David Pirotte <david@altosw.be>
Cc: 20423@debbugs.gnu.org
Subject: bug#20423: goops - inheritance of slot options
Date: Fri, 24 Jun 2016 07:04:43 +0200 [thread overview]
Message-ID: <87por7jhxw.fsf@pobox.com> (raw)
In-Reply-To: <20160623200857.1e0d3e51@capac> (David Pirotte's message of "Thu, 23 Jun 2016 20:08:57 -0300")
Hi,
On Fri 24 Jun 2016 01:08, David Pirotte <david@altosw.be> writes:
> It actually is my intention, it has been for years, to study, dig into and work on
> our GOOPS implementation and start to help maintain it ... if I only had more time,
> I would have done it already.
>
> Till then we rely on you
I don't have any time to devote to this, sorry :/
Regards,
Andy
next prev parent reply other threads:[~2016-06-24 5:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-25 2:05 bug#20423: goops - inheritance of slot options David Pirotte
2016-06-23 20:23 ` Andy Wingo
2016-06-23 23:08 ` David Pirotte
2016-06-24 1:06 ` dsmich
2016-06-24 5:04 ` Andy Wingo [this message]
2016-07-12 20:02 ` David Pirotte
2016-06-24 5:12 ` Andy Wingo
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=87por7jhxw.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=20423@debbugs.gnu.org \
--cc=david@altosw.be \
/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).