This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: tagging classpath for GCC import
- From: Matthias Klose <doko at ubuntu dot com>
- To: Mark Wielaard <mark at klomp dot org>
- Cc: classpath-patches at gnu dot org, GCC Java <java at gcc dot gnu dot org>
- Date: Mon, 03 Dec 2012 02:15:34 +0100
- Subject: Re: tagging classpath for GCC import
- References: <50BA49AE.3070403@ubuntu.com> <20121202212044.GA22310@toonder.wildebeest.org>
Am 02.12.2012 22:20, schrieb Mark Wielaard:
> Hi,
>
> Matthias wanted to import the latest classpath from git into libgcj
> so I have pushed a tag (libgcj-import-20121202) for current HEAD.
> (Note for future reference, to push a tag one uses git push --tags,
> with just git push the tag stays local.)
>
> 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.
Further, it looks like classpath did bump the requirement on autoconf to 2.69,
and didn't even bother to document that (m4/iconv.m4 requires macros only found
in 2.69). classpath itself pretends to require 2.63.
GCC has 2.64, and won't change for the next release. Any hint how to handle this
properly?
Matthias