Practical Perforce

Errata for Practical Perforce

Submit your own errata for this product.


The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update



Version Location Description Submitted By Date Submitted Date Corrected
Printed
Page vii
3rd paragraph

4th sentence of 3rd paragraph on page vii of the preface has a spelling error. "Documention," should read "Documentation,".

Anonymous   
Printed
Page x
Figure P-2

In the top-left bubble indicating the server, Perforce is misspelled Preforce.

Anonymous   
Printed
Page 28
1st paragraph of the TIP, 2nd sentence

Sentence reads: "The @> revision syntax, for example, is one them." Sentence should read: "The @> revision syntax, for example, is one of them."

Anonymous   
Printed
Page 34
3rd code snippet

p4 integrate projectA/... projectB/... edp4 submit "edp4" should be "p4"

Anonymous   
Printed
Page 42
first line, first paragraph

cparticular Should be:particular

Anonymous   
Printed
Page 44
examples in "Deleting depot files" (cont'd on page 45)

The paths in the "p4 sync" commands have an extra "w" instead of "c:wsdevwwww" Should be: "c:wsdevwww".

Anonymous   
Printed
Page 50
"The Ambiguities of SCM Terminology" inset

The "img tag" examples in the second bullet point should be in constant width font.

Anonymous   
Printed
Page 53
Example of "Resolving files automatically"

The sample command should be "p4 resolve -as", not just "resolve -as". Similar errors appear on pages 56 ("resolve -at") and 57 ("resolve -ay").

Anonymous   
Printed
Page 97
first paragraph of section "Integrating changes incrementally"

In the last sentence, "integating" Should be: "integrating"

Anonymous   
Printed
Page 104
second-last paragraph

In the last sentence, the word "you" is unnecessary Should be "...you'll be prompted to resolve...".

Anonymous   
Printed
Page 106
at the top of page

p4 integ //Ace/Main/...@3456 //Ace/V1/... should be: p4 integ //Ace/V1/...@3456 //Ace/Main/...

Anonymous   
Printed
Page 106
3rd paragraph (and Figure 4-17)

from author: "Compare this with figure 4-17" should read "Compare this with figure 4-16". "the symbol for MAIN/readme#11" should read "the symbols for MAIN/readme". Figure 4-17 doesn't quite match the example. The MAIN/readme has too many revisions. Its highest revision should be 9, connected by an arrow coming from V1/readme.

Anonymous   
Printed
Page 116
Second paragraph in "Keeping target files from being deleted" section

The second paragraph in the "Keeping target files from being deleted" section is redundant.

Anonymous   
Printed
Page 120
second paragraph, second sentence

"orginal" should be "original"

Anonymous   
Printed
Page 120
Item 2 in list

(from author) The "p4 integ" example is completely wrong. It should be: p4 integ -h -f //Ace/V1/db/Jamfile@3461,3461 //Ace/MAIN/db/Jamfile Also, the explanatory note that follows should say: The revision range @3461,3461 makes Perforce use @3460 as the merge base.

Anonymous   
Printed
Page 139
2nd example under "Searching for jobs"

Example says: p4 jobs -e "status=open user=carl|usr=ann login window|dialog siz*" Should say: p4 jobs -e "status=open user=carl|user=ann login window|dialog siz*"

Anonymous   
Printed
Page 170
first paragraph

"because we face deadlines and market pressures to face" should be: "because we face deadlines and market pressures".

Anonymous   
Printed
Page 173
fourth paragraph, third sentence

space missing between "feature" and "gives"

Anonymous   
Printed
Page 179
First paragraph

"DEVX" should be "DEVZ"

Anonymous   
Printed
Page 180
references to this page in the index

The "porting branches" heading on this page is indexed as "posting branches" and "branches, posting". Index needs to be changed.

Anonymous   
Printed
Page 193
Fifth list item

//Tango/Dist/ has a trailing slash that is not present on any of the other items.

Anonymous   
Printed
Page 205
"Nightly Builds", first sentence

"nightly" is misspelled "nighty"

Anonymous   
Printed
Page 221
first bullet in the box near top of page

"Once possibility is that..." should be: "One possibility is that..."

Anonymous   
Printed
Page 234
the last two "comm" program examples

The two comm program examples on this page need both the -1 and -3 options to get the desired results. The -1 option is missing from both. The examples should read: comm -1 -3 tempfile1 tempfile2 > tempfile3 comm -1 -3 tempfile4 tempfile5 > tempfile6

Anonymous   
Printed
Page 256
section titled "Workspace file filters"

The text says that Bob is adding filters to the AGUI-bob workspace view. Unfortunately the examples don't match the AGUI-bob view shown in the preceding section.

Anonymous   
Printed
Page 262
Last sentence in the box

"...by editing the its spec form." should be "...by editing its spec form." or "...by editing the spec form."

Anonymous   
Printed
Page 280
#3

//Ace/MAIN/utils/... //DONDEV-master/utils/... //Ace/MAIN/tests/... //DONDEV-master/tests/... Should be: //Ace/DONDEV/utils/... //DONDEV-master/utils/... //Ace/DONDEV/tests/... //DONDEV-master/tests/...

Anonymous   
Printed
Page 298
First paragraph in "Showstoppers in WEBQA" section

The URL does not match the scenario being discussed. The correct URL is "http://webmain.ace.com".

Anonymous