The history tab dynamically loads more of the version history when scrolling down, is there any way of loading the entire version history without having to tediously continue scrolling until you hit the first revision? The reason is that when you try and use the Find command it only considers the items in the list view that are currently loaded.
I agree with Bryan Pendleton's recommendation. Running via command line is quick and you can massage the results however you'd like. The only thing I would add is to check out the current documentation. Googling perforce documentation is unfortunately littered with old results. Bryan's links are 3 and 5 years old.
https://www.perforce.com/manuals/cmdref/Content/CmdRef/p4_filelog.html
https://www.perforce.com/manuals/cmdref/Content/CmdRef/p4_changes.html
Related
I am working on an ASP.NET application in VS2010; the repository is still VSS-2005. I am going to abandon the changes made to one of the pages and revert back to the version that existed two checkins ago (which is the current production code). My problem is that I haven't worked with VSS much and I've never done this particular thing before. I can't find any "How to" literature on VSS that tells how to do it, and when I try to do it using the intuitive thing (do a "Get" on the version I want to revert to), it does nothing.
I can View that older version using Notepad, and so I could check out the page and replace the code with the Viewed Notepad version, but this doesn't seem proper somehow.
I've been wondering about the Rollback button, but when I click it, it gives me an ominous message that I am not sure I like: "Rollback cannot be undone; some versions will be lost irretrievably! Continue anyway?"
Well, apparently there are no SourceSafe gurus out there, so I'll answer my own question. I bought a book! And it told me how to do it.
Overview:
Check out the current version manually
"Get" the version we want to revert to
Check in the older version as a newer version
Details:
Check out the current version, then use the View History command to show the History dialog and select the version that is desired to be reverted to.
After selecting/highlighting this version, click on the Get button. The Get dialog shows where the specific file version will be placed along with several options. By default the path in the To text box points to the file in our workspace, which is what we want. Don't select the "Make writable" option since the file in question is already under source control. Leave everything as defaulted, and click OK. In the next dialog, choose "Replace". SourceSafe gets the older verison and overwrites the one in the workspace.
Now that you have the older base version, all you have to do is check in the version and obtain a new version that is identical to the old one.
I got this information from the book "Visual Source Safe 2005 - Software Configuration Management in Practice" by Alexandru Serban, published by Packt Publishing Ltd. I bought the book used, but found you can still get it new from the publisher for a lot less than the list price -- $20 less! I don't know who might need a book about an obsolete source control system, but don't pay full price, get it from the publisher direct! Amazon charges the full list price on new copies (astonishing).
If I do "Reconcile Offline Work" in P4V, after a while the reconciling will finish and a window will eventually pop up showing the files that were modified, added, or removed. Sometimes I know the reconciling will take a few minutes or more based on the huge number of files in the directory, so I move on and start working on something else, and I expect that the reconciling will be done when I return later. However, sometimes, when I go back to P4V several minutes later, I see the window filled in with all of the modified, added, and removed files for a brief moment before they get blanked out and the scan seems to start all over again.
This can be quite aggravating since I'm trying to avoid having to sit around and wait for the reconciling to complete, but I end up having to wait for multiple reconciles when I only want to do it once.
Any ideas as to what causes this or how to turn off this repeated reconciling when I only want to reconcile once?
I'm using the "2014.3" version.
I did a bit of additional searching on this and finally stumbled upon the answer!
This is bug #70465: https://www.perforce.com/perforce/doc.current/user/p4vnotes.txt
#1171326 (Bug #70465)
There is now a preference to disable global refresh affecting the Reconcile
Offline Work dialog. Default is to continue allowing global refresh to
update the dialog. The preference can be found on the Behavior page in
preferences.
Updating to a newer version (2015.1 or newer) will allow me to disable the global refresh in the Preferences/Behavior menu.
I tried diging to find who wrote a certain line in a project.
I've Annotate the cs file notice there was a change couple of days ago..
When clicking "Compare With Previous" I notice that the last developer only added indent spaces.
I want to see the previous of that version.
My workaround is to use View History and start comparing.. But that's not fun.
Any clue how can I do that?
Have you tried doing a Get Specific version to download a previous version to your local workspace, then doing an Annotate. I think that should work.
I have the ProportionalResize plugin installed, but it throws the following error message (shown below) everytime I resize the whole GUI-WINDOW after performing a window split. I realize this is a Ingo Karkat plugin which makes use of the ingo-library (I use L9 as func library). But even with his lib installed the error message changes from
to
.
There is a comment in this and this file about the stale window dimensions (comment on revision 1.00.003). Can't say I understand what he talks about. Just stumbled upon it.
If you need my vimrc, let me know.
Plugin author here. I concur with the commenters that issues like these are best first addressed directly to the plugin's author (in my case, via the email address found in the documentation and scripts, since I don't use an issue tracker for these small plugins yet), not via Stack Overflow.
Because there is no VimResizedPre event, the plugin periodically (on CursorHold) records the current dimensions to be able to calculate the difference. When there's no current record, you'll get the Stale window dimensions record error. To avoid that, try waiting for 4 seconds before attempting the resize.
Resizing internal window splits (as you've reported) should not trigger that error, however, because the plugin is only triggered when the outer Vim window borders change, not when you adapt the internal window layout.
I have to write a small script to deploy a patch for our Application. The patch
will replace a couple of files in the application.I decided to depploy the patch using Applescript. The files to be copied are quite large and it takes some time for the files to be copied. I wanted to know if there is any way I can get a dialog box which doesn't block the execution of the script so that I can display some message like Updating.. etc while the patch is applied and then close the dialog box after wards.
Thanks
Shivaprasad
There's a scripting addition called Akua Sweets (oldy but goody) that has a display progress command. Get it at osaxen.com. it's in the 'most popular' section at the top of the page.
edit
Oh, bugger, that's only for OS9. It was really useful back in the day, I remember using it a lot (of course everything took a lot longer in those days so progress bars were more in demand).
another edit
You got me inspired, there's a couple of scripts I use that need progress bars, so I went looking and found this scripting addition at http://osaxen.com/files/extrasuites1.1.html
and again
here's a basic tutorial for how to do it in interface builder. I think that's probably the right way to do it.
I myself ran into the same problem. Unfortunately applescript doesn't provide an easy way of implementing a progress bar.
I ended up using the stop loop example found here to build an application. This guy has a bunch of applescript studio xcode projects to download and mess around with. It's some really great sample code if you aren't too familiar with applescript studio.