StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Regarding branching, I doubt you can "branch" locally in Perforce, nor could you natively stash.</p> <ul> <li>Git is based on a graph of commits (a <strong><a href="http://en.wikipedia.org/wiki/Directed_acyclic_graph" rel="nofollow noreferrer">DAG - Directed Acyclic Graph</a></strong> actually), which will display only the content of a commit (trees and blobs)</li> <li>Perforce is a <a href="https://stackoverflow.com/questions/645008/what-are-the-basic-clearcase-concepts-every-developer-should-know/645771#645771">linear VCS</a>, based on composition of selection rules (it will compose what to display based on local selection rules)</li> </ul> <p>Regarding branching:</p> <ul> <li>A branch in Git is just a path within the graph</li> <li>A branch in Perforce is: <ul> <li>a codeline (most likely meaning when used as a noun)</li> <li>a branch view specification (as in the entity created by "<code>p4 branch</code>" command - also a noun) - these are talked about below</li> <li>when used as a verb ("to branch") it means to use the "<code>p4 integrate</code>" command to create a new codeline (or branch!) of one or more files</li> </ul></li> </ul> <p>As mentioned in this <a href="http://www.vaccaperna.co.uk/scm/branching.html" rel="nofollow noreferrer">introduction to perforce branching</a>, Perforce, being heavily linked to its central depo, need to create the relevant metadata for each files to create a branch.<br> Git would only write some bits to register the creation of a new branch!</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload