I want to reverse the changes from one of my checkins. In the right-click context menu of the particular changelist, there are these two options:

 - Rollback...
 - Back Out Submitted Changelist &lt;number&gt;

What is the difference between these two? In what situations should I use either one?

What is the difference between &quot;Rollback...&quot; and &quot;Back Out Submitted Changelist #####&quot; in Perforce P4V

There is a lot of &quot;Git for Perforce users&quot; documentation out there, but seemingly very little of the opposite.

I have only used Git previously and recently started a job where I have to use Perforce a lot, and find myself getting very confused a lot of the time. The concepts I&#39;m used to from Git seem not to map to Perforce at all.

Is anyone interested in putting together a few tips for using Perforce for someone who is used to Git?

Perforce for Git users?

I&#39;m new to Perforce and have created a few workspaces as exercises for getting familiar with it. Now I would like to delete some of the workspaces. I just want to get rid of the workspaces so that they do not appear on the drop-down in the workspaces view (*do not* want to do anything with actual depot files).

Googling up an answer yields the suggestion to &quot;make the workspace active&quot; (I guess that means select it in the workspace dropdown?) and then delete it from the &quot;edit&quot; menu. Unfortunately, the delete option is grayed-out when I try this.

Anyone know how to do this, or do I just have to live with junk workspaces? I&#39;ve physically deleted one of them from the disk, and it still appears in the workspace drop down, and I can&#39;t even synchronise it with the depot now, so I guess that&#39;s not how to do it.


How to delete a workspace in Perforce (using p4v)?

A question that occasionally arises is what is the best way to determine the changelist that you last synced to in Perforce. This is often needed for things like injecting the changelist number into the revision info by the automatic build system.


Determining the last changelist synced to in Perforce

I sometimes use the feature &#39;Reconcile Offline Work...&#39; found in Perforce&#39;s P4V IDE to sync up any files that I have been working on while disconnected from the P4 depot. It launches another window that performs a &#39;Folder Diff&#39;.

I have files I never want to check in to source control (like ones found in bin folder such as DLLs, code generated output, etc.) Is there a way to filter those files/folders out from appearing as &quot;new&quot; that might be added. They tend to clutter up the list of files that I am actually interested in.  Does P4 have the equivalent of Subversion&#39;s &#39;ignore file&#39; feature? 

Can you &quot;ignore&quot; a file in Perforce?

When viewing submitted changelists in p4v, is there a way to display a particular changelist number?  That is, how I do the equivalent of `p4 describe` in p4v?  Can I filter for a particular changelist number?  I don&#39;t see how.


How do I display a particular changelist number in p4v?

Anybody have a script or alias to find untracked (really: unadded) files in a Perforce tree?

EDIT: I updated the accepted answer on this one since it looks like P4V added support for this in the January 2009 release.

How to find untracked files in a Perforce tree? (analogue of svn status)

I&#39;ve been using Perforce for a number of years. I&#39;d like to switch to using git for my personal code, but all of the git tutorials that I&#39;ve seen either assume that you&#39;e a complete source control n00b (which makes them incredibly tedious) or that you&#39;re used to svn (which I&#39;m not).

I know p4, and I also understand the idea behind a distributed source control system (so I don&#39;t need a sales pitch, thanks). What I&#39;d like is a translation table from p4 command to equivalent git commands, as well as the &quot;can&#39;t live without&quot; commands that have no p4 equivalent.

Since I suspect every p4 user uses a different subset of p4, here are some of the things I regularly do in p4 that I&#39;d like to be able to do in git that aren&#39;t immediately obvious from the docs I&#39;ve looked at:

 1. create multiple pending changelists in a single client. (`p4 change`)
 1. edit a pending changelist. (also `p4 change`)
 1. see a list of all of my pending changelists (`p4 changes -s pending`)
 1. list of all of the changed files in my client (`p4 opened`) or in a pending changelist (`p4 describe`)
 1. see a diff of a pending changelist (I use a wrapper script for this which uses `p4 diff` and `p4 describe`)
 1. for a given file, see which submitted changelists affected which lines (`p4 annotate`)
 1. for a given file, see a list of the descriptions of the changelists that affected the file (`p4 log`)
 1. submit a pending changelist (`p4 submit -c`)
 1. abort a pending changelist (`p4 revert`)


A lot of these revolve around &quot;changelists&quot;. &quot;changelist&quot; is p4 terminology. What&#39;s the git equivalent term?

It sounds like branches might be what git users use in place of what p4 calls changelists. A bit confusing, since p4 also has something called a branch though they seem to be only vaguely related concepts. (Though I always thought p4&#39;s concept of a branch was pretty weird it is different yet again from the classic RCS concept of a branch.)

Anyway... I&#39;m not sure how to accomplish what I normally do in p4 changelists with git&#39;s branches. In p4 I can do something like this:

    $ p4 edit a.txt
    $ p4 change a.txt
    Change 12345 created.

At this point I have a changlist that contains a.txt. I can edit the description and continue working without submitting the changelist. Also, if it turns out that I need to make some changes to some other files, like say a bugfix in some other layer of the code, I can do that in the same client:

    $ p4 edit z.txt
    $ p4 change z.txt
    Change 12346 created.

Now I have two separate changelists in the same client. I can work on these concurrently, and I don&#39;t need to do anything to &quot;switch between&quot; them. When it comes time to commit, I can submit them separately:

    $ p4 submit -c 12346  # this will submit the changes to z.txt
    $ p4 submit -c 12345  # this will submit the changes to a.txt

I can&#39;t figure out how to replicate this in git. From my experiments, it doesn&#39;t appear that `git add` is associated with the current branch. As far as I can tell, when I `git commit` it&#39;s going to commit all files that I `git add`-ed no matter what branch I was in at the time:

    $ git init
    Initialized empty Git repository in /home/laurence/git-playground/.git/
    $ ls
    a.txt  w.txt  z.txt
    $ git add -A .
    $ git commit
     Initial commit.
     3 files changed, 3 insertions(+), 0 deletions(-)
     create mode 100644 a.txt
     create mode 100644 w.txt
     create mode 100644 z.txt
    $ vi a.txt z.txt 
    2 files to edit
    $ git status
    # On branch master
    # Changed but not updated:
    #   (use &quot;git add &lt;file&gt;...&quot; to update what will be committed)
    #   (use &quot;git checkout -- &lt;file&gt;...&quot; to discard changes in working directory)
    #
    #	modified:   a.txt
    #	modified:   z.txt
    #
    no changes added to commit (use &quot;git add&quot; and/or &quot;git commit -a&quot;)
    $ git branch aardvark
    $ git checkout aardvark
    M	a.txt
    M	z.txt
    Switched to branch &#39;aardvark&#39;
    $ git add a.txt 
    $ git checkout master
    M	a.txt
    M	z.txt
    Switched to branch &#39;master&#39;
    $ git branch zebra
    $ git checkout zebra
    M	a.txt
    M	z.txt
    Switched to branch &#39;zebra&#39;
    $ git add z.txt 
    $ git status
    # On branch zebra
    # Changes to be committed:
    #   (use &quot;git reset HEAD &lt;file&gt;...&quot; to unstage)
    #
    #	modified:   a.txt
    #	modified:   z.txt
    #
    $ git checkout aardvark
    M	a.txt
    M	z.txt
    Switched to branch &#39;aardvark&#39;
    $ git status
    # On branch aardvark
    # Changes to be committed:
    #   (use &quot;git reset HEAD &lt;file&gt;...&quot; to unstage)
    #
    #	modified:   a.txt
    #	modified:   z.txt

In this example, the aardvark and zebra branches seem to contain exactly the same set of changes, and based on the output of `git status` it appears that doing a commit in either will have the same effect. Am I doing something wrong?

Git for Perforce users

So I&#39;m in the process of getting GIT sold at work. First thing I need is to convince everyone that GIT is better at what they&#39;re already used to doing. We currently use Perforce. Anybody else go through a similar sale? Any good links/advice?

One of the big wins is that we can work with it disconnected from the network. Another win IMO is the way adds/checkouts are handled. More points are welcome! Also we have about 10-20 devs total.

GIT vs. Perforce- Two VCS will enter... one will leave

On occasion, I find myself wanting to search the text of changelist descriptions in Perforce.  There doesn&#39;t appear to be a way to do this in P4V.  I can do it by redirecting the output of the changes command to a file...

    p4 changes -l &gt; p4changes.txt

...(the -l switch tells it to dump the full text of the changelist descriptions) and then searching the file, but this is rather cumbersome.  Has anyone found a better way?

How do you search the text of changelist descriptions in Perforce?

We&#39;re using Perforce and Visual Studio. Whenever we create a branch, some projects will not be bound to source control unless we use &quot;Open from Source Control&quot;, but other projects work regardless. From my investigations, I know some of the things involved:

In our .csproj files, there are these settings:

* &amp;lt;SccProjectName&gt;
* &amp;lt;SccLocalPath&gt;
* &amp;lt;SccAuxPath&gt;
* &amp;lt;SccProvider&gt;

Sometimes they are all set to &quot;SAK&quot;, sometimes not. It seems things are more likely to work if these say &quot;SAK&quot;.

In our .sln file, there are settings for many of the projects:

* SccLocalPath#
* SccProjectFilePathRelativizedFromConnection#
* SccProjectUniqueName#

(The # is a number that identifies each project.) SccLocalPath is a path relative to the solution file. Often it is &quot;.&quot;, sometimes it is the folder that the project is in, and sometimes it is &quot;..&quot; or &quot;..\\..&quot;, and it seems to be bad for it to point to a folder above the solution folder. The relativized one is a path *from* that folder to the project file. It will be missing entirely if SccLocalPath points to the project&#39;s folder. If the SccLocalPath has &quot;..&quot; in it, this path might include folder names that are not the same between branches, which I think causes problems.

So, to finally get to the specifics I&#39;d like to know:

* What happens when you do &quot;Change source control&quot; and bind projects? How does Visual Studio decide what to put in the project and solution files?
* What happens when you do &quot;Open from source control&quot;?
* What&#39;s this &quot;connection&quot; folder that SccLocalPath and SccProjectFilePathRelativizedFromConnection refer to? How does Visual Studio/Perforce pick it?
* Is there some recommended way to make the source control bindings continue to work even when you create a new branch of the solution?

---

*Added June 2012:*
I don&#39;t use Perforce any more, so I can&#39;t vouch for it, but have a look at &lt;a href=&quot;https://stackoverflow.com/a/11148342/2283&quot;&gt;KCD&#39;s answer&lt;/a&gt; below. Apparently there&#39;s &lt;a href=&quot;http://forums.perforce.com/index.php?/topic/1585-new-perforce-plugin-for-visual-studio-20121-beta-available-now/&quot;&gt;a new P4 VS plugin&lt;/a&gt; under development. Hopefully it should clear up all this mess!

How does Visual Studio&#39;s source control integration work with Perforce?

My team has been using SVN for a few years. We now have the option of switching to Perforce.

What would be the benefits (and pitfalls) of making such a switch?

What are the benefits of using Perforce instead of Subversion?

One of our team member (located in different region) has shelved changes in P4 with changelist 1234. 

Now, if I want to see what files are modified snf what are the changes, how can I do this? 

What is the P4 command that I should use to see the changes made by our team member?

How to view Shelved P4 Changes?

I&#39;ve just downloaded a 4.5GB depot to a location on my hard drive that is not ideal.

I&#39;d like to move the folder that Perforce now sees as the &quot;workspace&quot; folder (iPhone) to another folder on my hard disk (Project Name), and then use *that* folder as the workspace folder.

Is this possible, or do I need to download the entire depot again?

Thanks,
Dave

How do I move a Perforce &quot;workspace&quot; folder?

Is there an equivalent of svn&#39;s blame for Perforce on the command line? `p4 annotate` doesn&#39;t display usernames -- only changeset numbers (without ancestor history!).

I currently have to track code back through ancestors and compare against the filelog, and there just has to be an easier way -- maybe a F/OSS utility?

Perforce blame

We use Visual Studio, which generates lots of `bin` and `obj` directories. When I use **P4V**&#39;s &quot;Reconcile Offline Work&quot; feature, these appear in the &quot;Local files not in depot&quot; list.

I&#39;d like to exclude them. I found [this question][1], but that talks about files, and when I try what it suggests (adding the following to my workspace view), **it doesn&#39;t work**:

    //depot/Foo/... //Client/Foo/...
    -//depot/Foo/.../*.user //Client/Foo/.../*.user
    -//depot/Foo/.../bin/... //Client/Foo/.../bin/...
    -//depot/Foo/.../obj/... //Client/Foo/.../obj/...

It doesn&#39;t actually seem to work for files, either: the foo.csproj.user files are still displayed in the list.

Can I exclude directories from P4V? If so, how? What am I doing wrong?


  [1]: https://stackoverflow.com/questions/55449/can-you-ignore-a-file-in-perforce

All Perforce Solutions on Gang of Coders

Total of 16 Perforce Solutions

What is the difference between "Rollback..." and "Back Out Submitted Changelist #####" in Perforce P4V