Search code examples
gitversion-controlaccurev

Accurev externally, git internally

I’m working on a project using Accurev as a VCS. Since I’m not at all familiar with it, I’m wondering if it would be a good idea to use git “internally” - meaning I would use git locally, then doing the “official” commits with Accurev.

Would this be an OK approach?

If yes, I would naturally want to exclude git from the Accurev versioning. Is it sufficient to have a .acignore that looks something like this:

myproject/.git
myproject/.git/*
myproject/.gitignore

Thanks!

Solution

  • You should be able to use git and AccuRev side-by-side. You mignt need to tune your .acignore, though.
    From the AccuRev Help files:

    Examples

    A simple wild card pattern such as “*.doc” that is specified globally matches any of these names:

    docs/chap01.doc
    docs/manuals/chap01.doc
    docs/widgetproj/src/manuals/usergd/chap01.doc

    The pattern manuals/*.doc specified in docs/.acignore matches any of these names:

    docs/manuals/chap01.doc
    docs/manuals/chap02.doc

    ... but not these names:

    docs/manuals/usergd/src/chap01.doc
    docs/widgetproj/src/manuals/usergd/chap01.doc

    However, using ** to specify recursion as in manuals/***/*.doc or manuals/**/chap.doc will match any occurrence of *.doc or chap.doc in any directory underneath the docs/manuals directory. See Wildcards in Ignore Patterns on page 12 for more information on using **.