From: Peter Baumann <waste.manager@gmx.de>
To: David Hagood <david.hagood@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Import ClearCaase with history?
Date: Wed, 31 Mar 2010 17:39:05 +0200 [thread overview]
Message-ID: <20100331153905.GA14999@m62s10.vlinux.de> (raw)
In-Reply-To: <1270035189.2785.11.camel@chumley>
On Wed, Mar 31, 2010 at 06:33:09AM -0500, David Hagood wrote:
> I am trying to drag where I work into a more modern software development
> process, but I am getting resistance from one division that has a large
> amount of history for some projects in a Clearcase repository. If I
> could show them that we could import all that history into git, it would
> go a long way to removing that resistance.
>
> I've seen programs that purport to import Subversion (which is also
> good, as they also are using Subversion for other projects....) but do
> any such programs exist for Clearcase?
>
> I know that, in theory, it would be possible to
> for all checkins to Clearcase
> check out of Clearcase
> check into git
> done
>
> but that would take an incredibly long time in practice, wouldn't it?
>
I don't think you can build anything which will import from ClearCase
*without* loosing *some* history. At least I have build a script which imported
something from CC into git in my former job and allow me to sync bidirectional
with CC.
The problems where no bidirectional mapping exists are the following:
- CC is file based, where as GIT is tree (the whole repository) based
- This leads to problems where you merge a file on differen CC branches,
because in GIT a merge is only on the whole tree, so at least this
information is lost. (see cleartool lstree for a file with merges)
Peter
next prev parent reply other threads:[~2010-03-31 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 11:33 Import ClearCaase with history? David Hagood
2010-03-31 12:13 ` Jon Seymour
2010-03-31 12:16 ` Charles O'Farrell
2010-03-31 15:39 ` Peter Baumann [this message]
2010-03-31 16:09 ` Avery Pennarun
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=20100331153905.GA14999@m62s10.vlinux.de \
--to=waste.manager@gmx.de \
--cc=david.hagood@gmail.com \
--cc=git@vger.kernel.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 NNTP newsgroup(s).