From: Mark Wielaard <mark@klomp.org>
To: Andrew Haley <aph@redhat.com>
Cc: Matthias Klose <doko@ubuntu.com>,
classpath-patches@gnu.org, GCC Java <java@gcc.gnu.org>
Subject: Re: [cp-patches] tagging classpath for GCC import
Date: Mon, 03 Dec 2012 10:04:00 -0000 [thread overview]
Message-ID: <1354529065.3581.73.camel@bordewijk.wildebeest.org> (raw)
In-Reply-To: <50BC70F7.5050606@redhat.com>
On Mon, 2012-12-03 at 09:29 +0000, Andrew Haley wrote:
> On 12/03/2012 09:05 AM, Mark Wielaard wrote:
> > 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 that's not supposed to happen, surely. The transfer to GIT isn't
> complete until the tags have been copied.
There is the classpath git tree at
http://icedtea.classpath.org/mirror/git/classpath/classpath/
which does have all that. But it only has the CVS part of the history.
The trick now is to figure out how to merge that git tree with the
official GNU Classpath git tree on savannah. Sadly my git foo isn't
strong enough to figure that out :{
So any hints or tips from some more experienced git users appreciated.
Thanks,
Mark
next prev parent reply other threads:[~2012-12-03 10:04 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 [this message]
2012-12-03 10:44 ` Pekka Enberg
2012-12-03 12:31 ` Mark Wielaard
2012-12-03 15:00 ` Andrew Hughes
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=1354529065.3581.73.camel@bordewijk.wildebeest.org \
--to=mark@klomp.org \
--cc=aph@redhat.com \
--cc=classpath-patches@gnu.org \
--cc=doko@ubuntu.com \
--cc=java@gcc.gnu.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).