public inbox for mauve-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Andrew John Hughes" <gnu_andrew@member.fsf.org>
To: mauve-patches@sources.redhat.com
Subject: [builder] FYI: Cleanup updates
Date: Sat, 16 Feb 2008 00:17:00 -0000	[thread overview]
Message-ID: <20080216001639.GA24051@localhost.localdomain> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 543 bytes --]

This is the first of a series of patches to remove
some cruft from builder.  This gets rid of a few
dead updates (gcj-eclipse, generics) and fixes
cacao so we are using the hg development tree and
not the dead svn repository.

ChangeLog:

2008-02-16 Andrew John Hughes <gnu_andrew@member.fsf.org>

	* Update: Remove generics, gcj-eclipse
	and future branches.  Fix cacao to use hg.

-- 
Andrew :)

Support Free Java!
Contribute to GNU Classpath and the OpenJDK
http://www.gnu.org/software/classpath
http://openjdk.java.net

[-- Attachment #1.2: cleanup-01.diff --]
[-- Type: text/x-diff, Size: 1883 bytes --]

Index: Update
===================================================================
RCS file: /cvs/mauve/builder/scripts/Update,v
retrieving revision 1.5
diff -u -3 -p -u -r1.5 Update
--- Update	30 Jan 2008 20:06:09 -0000	1.5
+++ Update	16 Feb 2008 00:13:16 -0000
@@ -15,11 +15,6 @@ Status "svn update gcc"
 cd $TOP/gcc/trunk
 ./contrib/gcc_update
 
-# gcc gcj-eclipse branch
-Status "svn update gcc gcj-eclipse branch"
-cd $TOP/gcc/gcj-eclipse
-./contrib/gcc_update
-
 # Classpath.
 Status "cvs update classpath"
 cd $TOP/classpath
@@ -27,22 +22,6 @@ cvs -d :pserver:anonymous@cvs.savannah.g
 cd classpath
 ./autogen.sh
 
-# Classpath generics
-Status "cvs update classpath generics branch"
-cd $TOP/generics
-cvs -d :pserver:anonymous@cvs.savannah.gnu.org:/cvsroot/classpath co \
-  -rgenerics-branch classpath
-cd classpath
-./autogen.sh
-
-# Classpath future release
-#Status "cvs update classpath future release branch"
-#cd $TOP/classpath-future-release
-#cvs -d :pserver:anonymous@cvs.savannah.gnu.org:/cvsroot/classpath co \
-#  -rclasspath-0_92-branch classpath
-#cd classpath
-#./autogen.sh
-
 # Mauve.
 Status "cvs update mauve"
 cd $TOP/mauve
@@ -63,18 +42,16 @@ ACLOCAL=aclocal-1.9 AUTOMAKE=automake-1.
 Status "cvs update jamvm"
 cd $TOP/jamvm
 cvs -d:pserver:anonymous@cvs.jamvm.berlios.de:/cvsroot/jamvm co jamvm
-cd jamvm
 
 # Jamvm
-Status "cvs update jamvm future release"
-cd $TOP/jamvm-future-release
-cvs -d:pserver:anonymous@cvs.jamvm.berlios.de:/cvsroot/jamvm co jamvm
-cd jamvm
+Status "cvs update jamvm release"
+cd $TOP/jamvm-release
+cp -r $TOP/jamvm/jamvm .
 
 # Cacao
-Status "svn update cacao"
+Status "hg update cacao"
 cd $TOP/cacao
-svn co svn://c1.complang.tuwien.ac.at/ahome/cacao/svn/cacao/trunk cacao
+hg clone http://mips.complang.tuwien.ac.at/hg/cacao/
 cd cacao
 ./autogen.sh
 

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2008-02-16  0:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20080216001639.GA24051@localhost.localdomain \
    --to=gnu_andrew@member.fsf.org \
    --cc=mauve-patches@sources.redhat.com \
    /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).