From: "Shawn O. Pearce" <spearce@spearce.org>
To: Graeme Geldenhuys <graemeg@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Team Coherence to Git conversion
Date: Tue, 30 Jun 2009 07:41:28 -0700 [thread overview]
Message-ID: <20090630144128.GR11191@spearce.org> (raw)
In-Reply-To: <h2cmv6$agp$1@ger.gmane.org>
Graeme Geldenhuys <graemeg@gmail.com> wrote:
> We have a couple (actually around 20) projects sitting in Team
> Coherence repositories. Luckily they have very little history. Before
> I joined the company nobody used revision control software - just
> simple zip archives once a week (if that many).
>
> Does anybody know of a tool that can convert a TC repository to
> Git? TC seems to be dying a slow dead, and I don't want our code
> to get trapped in proprietary software we can't access, a few years
> down the line.
Huh. TC reminds me of PVCS Version Manager. Lots of hype on
the web page, but a tool from the early 1980s that still can't
do anything useful. Hell, it might be a rebranded PVCS VM.
No, there aren't any existing import tools from TC, in fact probably
nobody here has even heard of TC before. You are on your own to
write an import tool.
You might want to look at using git-fast-import to handle the git
side of the conversion, but you'll need to write your own script
to mine the data out of TC and format it for git-fast-import.
Look at contrib/fast-import for some examples, and the fast-import
man page is rather extensive.
--
Shawn.
next prev parent reply other threads:[~2009-06-30 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 9:45 Team Coherence to Git conversion Graeme Geldenhuys
2009-06-30 14:41 ` Shawn O. Pearce [this message]
2009-07-01 8:00 ` Graeme Geldenhuys
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=20090630144128.GR11191@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=graemeg@gmail.com \
/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 NNTP newsgroup(s).