10 messages in com.perforce.perforce-user[p4] CVS to Perforce command mappings?| From | Sent On | Attachments |
|---|---|---|
| Todd Short | 02 Dec 2002 12:36 |  .dat |
| Dave Hildebrandt | 03 Dec 2002 09:01 | |
| Robert Cowham | 03 Dec 2002 09:31 | |
| Mike Castle | 03 Dec 2002 09:32 | |
| Arnt Gulbrandsen | 03 Dec 2002 09:42 | |
| Jeremy S. Russell | 03 Dec 2002 09:59 | |
| Todd Short | 03 Dec 2002 10:36 | |
| Bennett, Patrick | 03 Dec 2002 13:15 | |
| Todd Short | 03 Dec 2002 13:52 | |
| John Marshall | 03 Dec 2002 15:33 |
| Subject: | [p4] CVS to Perforce command mappings? |
|---|---|
| From: | Robert Cowham (rob...@vaccaperna.co.uk) |
| Date: | 12/03/2002 09:31:33 AM |
| List: | com.perforce.perforce-user |
cvs diff: is a big one, diff'ing by version number, diff'ing your working version with the head. Recursivly diffing a folder...
Doable via p4 diff. In p4win try from Revision History.
cvs annotate: I don't know if anyone else uses this, but I find it handy. It what it does is gets the file and details each line with who checked it in and what version the line changed, like this
new function in 2002.2 - p4 annotate (also available in p4win from File menu)
C:\Data\work\www>p4 -p 1777 help annotate
annotate -- Print file lines along with their revisions
p4 annotate [ -aq ] file[revRange] ...
Prints all lines of the named files, indicating what revision introduced each line into the file.
If the file argument has a revision, then only revisions up to that revision are displayed. If the file argument has a revision range, then only revisions within that range are displayed. See 'p4 help revisions' for help specifying revisions.
The -a flag includes both deleted files and lines no longer present at the head revision; in this case, both the starting and ending revision for each line is indicated.
The -q flag suppresses the one-line header for each file.
Try browsing the public depot using p4web and select the option Show "fully annotated text file" on something (with more than one version!)
cvs tag: for creating tags and branches.
Can use p4 label/labelsync to create labels. Obviously p4 integ/branch for the branching bit.
Robert