public inbox for
 help / color / mirror / Atom feed
From: Andreas Rottmann <>
To: Greg Troxel <>
Subject: Re: guile-gobject problem [solved], g-wrap
Date: Tue, 12 Aug 2003 16:31:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> (Greg Troxel's message of "12 Aug 2003 11:29:45 -0400")

Greg Troxel <> writes:

> [I fixed the spelling of Rob's username - it was rbl in your mail.]
[I already re-sent it to him]

>   I've found & fixed the bug. I'll commit to CVS (just have been given
>   access by Marius!), after posting a patch here for review. First,
>   however, I'd like to discuss (once again ;-)), the forking of
>   g-wrap. I could check in a g-wrap into the guile-gtk CVS repository
>   that provides:
[some nice features]

> Not that I know what's really up, but note that gnucash is said to be
> short of developer cycles.
Yes, I've read the article on LWN.

> So creating a g-wrap _project_ on savannah, rather than putting it
> under guile-gtk, and trying to make sure (a bit) it still works for
> other uses, and perhaps a release, might be a real contribution.
There is already a g-wrap project on savannah, owned by Rob. There is
no code in CVS ATM. If Rob would give me CVS write access, I'd be
happy to check my modified version in. He could then lart me on any
ugly things I've done with his code ;-), and I'll try to bring it in
shape again.

Regards, Andy
Andreas Rottmann         | Rotty@ICQ      | 118634484@ICQ | | GnuPG Key:
Fingerprint              | DFB4 4EB4 78A4 5EEE 6219  F228 F92F CFC5 01FD 5B62

Latein ist das humanoide Äquivalent zu Fortran.
   -- Alexander Bartolich in at.linux

  reply	other threads:[~2003-08-12 16:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-11 20:30 guile-gobject problem Andreas Rottmann
2003-08-12 14:49 ` guile-gobject problem [solved], g-wrap Andreas Rottmann
2003-08-12 15:29   ` Greg Troxel
2003-08-12 16:31     ` Andreas Rottmann [this message]
2003-08-12 17:00       ` Rob Browning
2003-08-15 13:19 ` guile-gobject problem Andy Wingo
2003-08-15 13:58   ` Andreas Rottmann

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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).