From: Andrew Hughes <gnu.andrew@redhat.com>
To: Matthias Klose <doko@ubuntu.com>
Cc: classpath-patches@gnu.org, GCC Java <java@gcc.gnu.org>,
Mark Wielaard <mark@klomp.org>
Subject: Re: tagging classpath for GCC import
Date: Mon, 03 Dec 2012 15:00:00 -0000 [thread overview]
Message-ID: <1386677132.9650803.1354546794742.JavaMail.root@redhat.com> (raw)
In-Reply-To: <50BBFD36.50906@ubuntu.com>
----- Original Message -----
> 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.
>
Try reading the mailing list. It's been discussed at length at the time
and there's been discussion of commits to it since.
> 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?
>
Classpath works with 2.63 on RHEL6. That's why I lowered it.
What macros are you referring to? iconv.m4 is dated 2002 in the header.
> Matthias
>
>
--
Andrew :)
Free Java Software Engineer
Red Hat, Inc. (http://www.redhat.com)
PGP Key: 248BDC07 (https://keys.indymedia.org/)
Fingerprint = EC5A 1F5E C0AD 1D15 8F1F 8F91 3B96 A578 248B DC07
prev parent reply other threads:[~2012-12-03 15:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50BA49AE.3070403@ubuntu.com>
[not found] ` <20121202212044.GA22310@toonder.wildebeest.org>
2012-12-03 1:15 ` Matthias Klose
2012-12-03 7:15 ` Matthias Klose
2012-12-03 9:05 ` Mark Wielaard
2012-12-03 9:29 ` [cp-patches] " Andrew Haley
2012-12-03 10:04 ` Mark Wielaard
2012-12-03 10:44 ` Pekka Enberg
2012-12-03 12:31 ` Mark Wielaard
2012-12-03 15:00 ` Andrew Hughes [this message]
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=1386677132.9650803.1354546794742.JavaMail.root@redhat.com \
--to=gnu.andrew@redhat.com \
--cc=classpath-patches@gnu.org \
--cc=doko@ubuntu.com \
--cc=java@gcc.gnu.org \
--cc=mark@klomp.org \
/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).