From: Mark Wielaard <mark@klomp.org>
To: Matthias Klose <doko@ubuntu.com>
Cc: classpath-patches@gnu.org, GCC Java <java@gcc.gnu.org>
Subject: Re: tagging classpath for GCC import
Date: Mon, 03 Dec 2012 09:05:00 -0000 [thread overview]
Message-ID: <1354525513.3581.13.camel@bordewijk.wildebeest.org> (raw)
In-Reply-To: <50BBFD36.50906@ubuntu.com>
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
next prev parent reply other threads:[~2012-12-03 9:05 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 [this message]
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
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=1354525513.3581.13.camel@bordewijk.wildebeest.org \
--to=mark@klomp.org \
--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).