perforce

Not sure if this is possible or not, but I figured I'd ask to see if anyone knows. Is it possible to find a file containing a string in a Perforce repository? Specifically, is it possible to do so without syncing the entire repository to a local directory first? (It's quite large - I don't think I'd have room even if I deleted lots of stuff - that's what the archive servers are for anyhow.) There's any number of tools that can search through files in a local directory (I personally use Agent Ransack, but it's just one of many), but these will not search a remote Perforce directory, unless

I am migrating a project to Maven and as we were used to always reference our builds by the latest change number in our Perforce SCM repository, I would like to be able to extract this information I am trying to configure Maven scm plugin via following resources: http://maven.apache.org/scm/maven-scm-plugin/usage.html for generic usage http://www.perforce.com/perforce/doc.current/manuals/p4maven/index.html First I don't understand how to make it work, so if anybody has a fully working example, I will be happy to, on my side I have tried by adding in my pom: <scm> <connection> scm:perforce

I use perforce for my revision control, when I hit 'p4 change' it always opens up the list on emacs, and we all know the pain of deleting text in it. How do i change it to gedit or vim or anything else? My default text editor is gedit. On the command line, set P4EDITOR either as an environment variable or in the P4CONFIG file. From the command line, p4 set P4EDITOR="C:\File Editor\editor.exe" You can test that this was successfull by running the following command after, which should launch your desired editor. p4 workspace user3571625 I had similar problem on my Windows system. It always used

I know this has come up before, but there was little in the way of day to day personal experiences in the posts I saw. Only a couple of responses. I'd love to hear from people that use git-p4, or have used git "under the covers" in a Perforce repo, or preferably both. And for those people who just use git underneath another version control, I'd love to hear how you deal with notifying the main version control of changes. Specifically, with git/perforce, when you're done and ready to commit the changes to the perforce server, how do you deal with telling perforce what changes there's been? I've

My workflow for testing my changes to our source code on a remote machine is the following: 1) On local machine: Shelve changes that I'd like to test 2) On remote machine (ssh): $ p4 revert //... $ p4 sync $ p4 unshelve -s <changelist number> $ ./run_test_scripts This seems to work fine when I've only made changes to files that already exists. If I've added new files these will be created during p4 unshelve , but not deleted during p4 revert . The documentation says that this is what p4 revert does so it isn't unexpected, but causes some problems if I want to test the same files again: $ p4

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

Is there a way to tell Perforce to leave text files alone without setting the file-type as binary? Or barring that, is there a way to tell the Perforce client to diff binaries? Binary usually isn't desirable, because I lose the ability to diff. To clarify: If I edit and make changes to a *.txt file on my window client, newlines will have CR+LF as per the DOS format. But if I P4 sync on a Unix client, it will have LF only. I need Perforce to keep the format as-is, regardless of where the Perforce client lives. That said, I do have a work-around: Set file-type as binary; and/or create a branch