From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18777 invoked by alias); 3 Dec 2012 09:05:29 -0000 Received: (qmail 18672 invoked by uid 22791); 3 Dec 2012 09:05:26 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from wildebeest.demon.nl (HELO gnu.wildebeest.org) (212.238.236.112) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 03 Dec 2012 09:05:20 +0000 Received: from wildebeest.demon.nl ([212.238.236.112] helo=[172.31.17.37]) by gnu.wildebeest.org with esmtp (Exim 4.63) (envelope-from ) id 1TfRxg-00057p-N7; Mon, 03 Dec 2012 10:05:17 +0100 Subject: Re: tagging classpath for GCC import From: Mark Wielaard To: Matthias Klose Cc: classpath-patches@gnu.org, GCC Java In-Reply-To: <50BBFD36.50906@ubuntu.com> References: <50BA49AE.3070403@ubuntu.com> <20121202212044.GA22310@toonder.wildebeest.org> <50BBFD36.50906@ubuntu.com> Content-Type: text/plain; charset="UTF-8" Date: Mon, 03 Dec 2012 09:05:00 -0000 Message-ID: <1354525513.3581.13.camel@bordewijk.wildebeest.org> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Spam-Score: -1.9 (-) X-IsSubscribed: yes Mailing-List: contact java-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-owner@gcc.gnu.org X-SW-Source: 2012-12/txt/msg00004.txt.bz2 On Mon, 2012-12-03 at 02:15 +0100, Matthias Klose wrote: > Am 02.12.2012 22:20, schrieb Mark Wielaard: > > It seems the git import from CVS lost the old tags. Does anybody > > know of a way to get them from the original CVS history into the > > git repository? > > I had a hard time getting any clue that the CVS repo was abandoned. Now finally > found http://savannah.gnu.org/git/?group=classpath which is not that obvious > when you start at classpath.org. Ah, sorry. That must make it look like GNU Classpath is even less active than it is :{ It is good to keep the CVS repo around for some time, just for the historical information like branches and tags that didn't transfer to the git repo. But not if people get confused by it and don't know where the current sources are. Maybe we should add a file to CVS "README_MOVED_TO_GIT" with information where the actively maintained sources are now found? Cheers, Mark