git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Import ClearCaase with history?

From
Avery Pennarun <apenwarr@gmail.com>
Date
Mar 31, 2010, 16:09 UTC
Message-ID
<o2w32541b131003310909p6558be4dxaaf0b277b149c82b@mail.gmail.com>
In-Reply-To
<20100331153905.GA14999@m62s10.vlinux.de>
On Wed, Mar 31, 2010 at 11:39 AM, Peter Baumann <waste.manager@gmx.de> wrote:
Show 8 quoted lines
> On Wed, Mar 31, 2010 at 06:33:09AM -0500, David Hagood wrote:
> 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)

Of course, you can do such file-by-file merges in CVS and SVN as well, and importing into git seems to work okay. What doesn't get tracked is the actual merge history of the merged files. This isn't such a problem when importing CVS and SVN, which mostly don't track merge history anyway :)

Have fun,
Avery
Previous: Peter Baumann
Message 5 of 5 in “Import ClearCaase with history?”
  1. David HagoodMar 31, 2010
  2. Jon SeymourMar 31, 2010
  3. Charles O'FarrellMar 31, 2010
  4. Peter BaumannMar 31, 2010
  5. Avery PennarunMar 31, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.