For those using CVS and wondering how to switch over to the stable 1.2 branches of glib and gtk+, here is the information I got off gnome-hackers. If you don't use CVS, ignore this message. James. -- Email: [EMAIL PROTECTED] WWW: http://www.daa.com.au/~james/ ---------- Forwarded message ---------- Date: Sat, 27 Feb 1999 02:14:33 +0100 (CET) From: Tim Janik <[EMAIL PROTECTED]> To: Gtk+ Developers <[EMAIL PROTECTED]> Cc: Hacking Gnomes <[EMAIL PROTECTED]> Subject: glib-1.3 and gtk+-1.3 branches hi fellow hackers, i've just branched glib and gtk+ on cvs so the HEAD version is 1.3.0 for both now. as experience with the 1.2.x line has shown, the 1.3 version is most probably going to be under heavy development for the next few weeks (months) and probably also imposing certain instabilities (even API wise ;). for application development, it is therefore recommended to work with glib's and gtk+'s 1.2.x version, so please people, update your trees with </usr/src/glib>$ cvs update -r glib-1-2 -d -P -R and </usr/src/gtk+>$ cvs update -r gtk-1-2 -d -P -R or for fresh checkouts: </usr/src>$ cvs -d :pserver:[EMAIL PROTECTED]:/debian/home/gnomecvs checkout -r glib-1-2 glib </usr/src>$ cvs -d :pserver:[EMAIL PROTECTED]:/debian/home/gnomecvs checkout -r gtk-1-2 gtk+ for people doing glib and/or gtk+ development, stability patches have to be applied against the glib-1-2 and gtk-1-2 revisions respectively, they will be merged into the HEAD revision once per week or so. please do *not* apply stability patches to the HEAD version, since back-merging is far more tedious and has to be done by hand. before major changes are to be applied to files in the HEAD (i.e. 1.3.x) tree, please ensure that any pending changes from the stable branch are merged into the devel tree first, e.g. </usr/src/gtk+-1.3/docs>$ cvs update -j gtk-1-2 refcounting.txt </usr/src/gtk+-1.3/docs>$ cvs commit -m "1.2.x merges" refcounting.txt --- ciaoTJ To unsubscribe: echo "unsubscribe" | mail [EMAIL PROTECTED]
