Perforce Helix Core Quick Start
Perforce Local Agate Network ssl:192.168.1.21:1666
P4 Glossary | Descriptions | Git Relate-ables | Reference Links |
---|---|---|---|
Depot | depots contain every revision of every file under version management. | Remote Repository | https://www.perforce.com/manuals/cmdref/Content/CmdRef/p4_depot.html#Description_..847 |
Stream | branches with | ||
additional intelligence | Branch | https://www.perforce.com/manuals/p4guide/Content/P4Guide/chapter.streams.html | |
Workspace | A workspace is a local folder on each user's personal computer for: |
- downloading files from the server's depot, and
- uploading your files to share with the members of your team. | Local Repository | https://www.perforce.com/manuals/p4v/Content/P4V/using.workspaces.html | | Copy Up | copy changes up to a more stable stream propagating a duplicate of the less stable stream. | Merge to more stable branch | https://www.perforce.com/manuals/p4v/Content/P4V/streams.merge_copy.html | | Merge Down | To merge changes down to a less stable stream | Merge from more stable branch | https://www.perforce.com/manuals/p4v/Content/P4V/streams.merge_copy.html | | Stream Path and Views | | Git Attribute, Git Config, Git Ignore, git module (But Branch Scoped) | https://www.perforce.com/manuals/p4guide/Content/P4Guide/streams.paths.html | | ChangeLists | | Commit | | | Check Out | | git lfs lock | | | Submit | | git push | |
Versioning Concept : Mainline Model
Balancing stability and innovation: the mainline model
Perforce Helix Core Branch Versioning Strategy
Perforce Helix Core 101
Branching: branches versus streams
Perforce Branching and Streams Difference
No Comments