accurev

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! You should be able to use git and AccuRev side-by-side. You mignt need to tune your .acignore, though. From the AccuRev Help

What is the difference between diff against basis and diff against backing in Accurev? I assume from your other posts in this forum that the context here would be in doing a diff of a file in your workspace against either Backed or Basis. Diff against Basis is going to compare the file you currently have in your workspace with the version that you starting working with prior to making your changes. An example would be, you update your workspace, begin working on foo.c that is (backed) status, make several modifications to it and then run Diff against Basis. It will compare your modifications

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 6 years ago . I am interested in the value (or lack thereof) of using a traditional SCM product (ClearCase, AccuRev, Perforce, etc.) along with Git for large projects with distributed teams. Is there a significant value-add in terms of increased

Does anyone use Accurev for Source Control Management? We are switching (eventually) from StarTeam to Accurev. My initial impression is that the GUI tool is severely lacking, however the underlying engine, and the branches as streams concept is incredible. The biggest difficulty we are facing is assessing our own DIY tools that interfaced with starteam, and either replacing them with DIY new tools, or finding and purchasing appropriate replacements. Additionally, is anyone using the AccuWork component for Issue management? Starteam had a very nice change request system, and AccuWork does not

My company uses Accurev for source control, and for all its benefits, there's one simple action that I just can't figure out how to accomplish. Often we have someone accidentally push a file up too far in our stream structure -- from the "Development" stream to the "Release" stream, for example. What is the best way to "un-promote" this file? That is to say, to get the old version of the file back into the "Release" stream, and keep the new version of the file in the "Development" stream, where it belongs? Just doing a "Revert to Backed" or other Revert action on the file in the Release stream