public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Stan Pinte <stan@altosw.be>
To: Marius Vollmer <marius.vollmer@uni-dortmund.de>
Cc: guile-gtk@sources.redhat.com,Ariel Rios <ariel@gnu.org>
Subject: Re: (gnome gtk) et al
Date: Tue, 06 May 2003 15:45:00 -0000	[thread overview]
Message-ID: <20030506172451.7a79df7b.stan@altosw.be> (raw)
In-Reply-To: <lj1xzc5buz.fsf@troy.dt.e-technik.uni-dortmund.de>

On 06 May 2003 17:33:08 +0200
Marius Vollmer <marius.vollmer@uni-dortmund.de> wrote:

> Stan Pinte <stan@altosw.be> writes:
> 
> > I believe that, in the current gnome-guile CVS (on cvs.gnome.org),
> > we find an outdated version of guile-gtk.
> 
> Yes.
> 
> > I am trying to replace that version with the current
> > guile-gtk-1.2-0.31,
> 
> What about moving the rest of the Gnome CVS over to Savannah?  That
> was the plan, but I don't know how far Ariel has come on the Gnome
> front.

For me, it would even be better: all on Savannah...

I made the test this morning, and the whole stuff compiles. I don't know yet if it runs...

Ariel, if I send you a tarball with the stuff to put in Savannah, is it ok?

Or do you prefer me to check it in?

Stan.

> 
> > I think the next step is to make the latest code from the guile-gtk
> > CVS a dependency of the gnome-guile CVS...
> 
> What does that mean?
> 


-- 

+----------------   Stanislas Pinte   ------------------+
|                   Sales Director                      |
|                                                       | 
|                 Alto Software sprl	                |
|               http://www.altosw.be/          		| 
|							|
|              cell:	 32 476 340 841		        |
|             email:	 stan@altosw.be          	|
+-------------------------------------------------------+

  reply	other threads:[~2003-05-06 15:45 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030407144511.GA1489@lark>
2003-04-07 19:57 ` Ariel Rios
2003-04-07 20:15   ` Andreas Rottmann
2003-04-08 10:34     ` Marius Vollmer
2003-04-08 14:56   ` Stan Pinte
2003-04-08 20:03     ` Andreas Rottmann
2003-04-08 21:33       ` David Pirotte
2003-04-11  4:48         ` Steve Tell
2003-04-11 10:00           ` Andreas Rottmann
2003-04-09 15:24       ` Stan Pinte
2003-04-10 17:05         ` Andreas Rottmann
2003-04-10 17:10           ` David Pirotte
2003-05-06  6:52     ` Stan Pinte
2003-05-06 15:33       ` Marius Vollmer
2003-05-06 15:45         ` Stan Pinte [this message]
2003-05-07 13:07           ` Stan Pinte
2003-05-07 14:02             ` Stan Pinte
2003-05-07 14:10               ` Marius Vollmer
2003-05-07 14:38                 ` Stan Pinte
2003-05-07 15:17                   ` Stan Pinte
2003-05-07 18:16                     ` Marius Vollmer
2003-05-08 11:43                       ` Stan Pinte
2003-05-12 14:18                         ` Stan Pinte
     [not found]                           ` <1052750737.26632.4.camel@tosca.elektra.com.mx>
2003-05-12 16:48                             ` Stan Pinte
2003-05-14  9:17   ` Andy Wingo
2003-05-16 14:26     ` Andreas Rottmann
2003-05-20 20:08       ` Andreas Rottmann
2003-05-23 22:00         ` Kevin Ryde
2003-05-26 13:04           ` Andreas Rottmann
2003-06-23 14:14   ` 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

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

  git send-email \
    --in-reply-to=20030506172451.7a79df7b.stan@altosw.be \
    --to=stan@altosw.be \
    --cc=ariel@gnu.org \
    --cc=guile-gtk@sources.redhat.com \
    --cc=marius.vollmer@uni-dortmund.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).