Perforce



  • Does anyone know Perforce Version Control System well?



  • I used to, but that was four years ago. I recall that I really didn't like it initially, but got used to used it pretty quickly. I very much liked the fact that you batch up a number of file check-ins as a single transaction. If one file didn't go through, e.g., because it needed to be merged, the whole transaction got rolled back. The result was that you would not break the build by checking in only some of your interdependent changes.



  • One of the most important things that version control can do for you is automatically make copies of your work on a drive or machine other than your development drive. Your development drive takes a lot of abuse, and having a copy of your work on another disk increases your safety margin. Not that you should use this in place of a regular backup strategy, but it can help.

    -------------------

    Nickysam



  • @nickysam said:

    One of the most important things that version control can do for you is automatically make copies of your work on a drive or machine other than your development drive.
     

    Forgive my lack of knowledge, but are we assuming that Perforce does this for you?  Kindof neat that the RCS will do that for you.  My old method was to set up a post-save hook in Vim to save a second copy of my file to a mirrored directory on a server.  But whatever works :)



  • @skippy said:

    @nickysam said:

    One of the most important things that version control can do for you is automatically make copies of your work on a drive or machine other than your development drive.
     

    Forgive my lack of knowledge, but are we assuming that Perforce does this for you?  Kindof neat that the RCS will do that for you.  My old method was to set up a post-save hook in Vim to save a second copy of my file to a mirrored directory on a server.  But whatever works :)

     

    I suppose any text editor that lets you modify its backup dir path will work, in that respect. :)



  • ok, here is a question I have

    I have been asked to "revert" a change that I made

     I figure that that is no problem.  I go to a command line interface and I log into perforce.  Then I type:

    p4 revert "the version number" "the filename with path"

    Of course I gave it the actual version number to revert and the actual filename with path.

    It gave me two errors:

    "the version number"  - file(s) not opened on this client.
    "the filename with path" - file(s) not opened on this client.

     



  • OK, an easier question.
    How do I merge to files in Perforce. Specifically, I want to merge a project file.


Log in to reply