The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
| Version |
Location |
Description |
Submitted by |
Date submitted |
| Printed |
Page 22
2nd bullet on page |
Actually, in modern versions of Perforce, you do not have to create the workspace root directory manually. Perforce will
create it when you run "p4 sync".
|
Anonymous |
|
| Printed |
Page 22
second bullet |
(You must create this directory yourself. Perforce will create its subdirectories for you, but it won't create the root
directory.)
This is incorrect. I've used serveral versions of Perforce on Macintosh and Windows operating systems and Perforce does
create the root workspace directory when files are sync-ed.
|
Anonymous |
|
| Printed |
Page 25
Last two sentences in "Setting the current workspace" |
The text reads:
"P4V offers you a list of workspaces to choose from when you launch it. The P4CLIENT setting in your environment doesn't affect P4V".
In P4V 2008.2, the P4CLIENT environment setting can affect P4V. In Edit->Preferences, Connection tab there is a setting
"When the application launches:".
If the user chooses
"Open the workspace that matches your Perforce environment settings"
then the P4CLIENT environment setting is respected and the user is not presented with a list of workspaces to choose from.
|
smithmw |
Jul 22, 2009 |
| Printed |
Page 27
second example |
p4 sync "//.../*.png"
is more concisely expressed as
p4 sync //....png
That is 4 dots instead of 3 no * and no need for quotes.
|
Anonymous |
|
| Printed |
Page 47
Last paragraph |
" because its format isn't acceptible "
should be "isn't acceptable"
|
Anonymous |
|
| Printed |
Page 58
3rd paragraph 2nd sentence under "Resolving files by merging theirs into yours" |
The sentence "In other words, resolving them requires merging, and merging requires updating your local files, so it's not considered safe.
Should read "In other words, resolving them requires merging, so it's not considered safe."
A "safe resolve" can modify your local files in the case where the "theirs" file has changes, but the "yours" file does not.
|
smithmw |
Aug 04, 2009 |
| Printed |
Page 106
first command line in example |
The filespecs on the command line are backwards.
should be:
p4 integ //Ace/V1/...@3456 //Ace/MAIN/...
|
Anonymous |
|
| Printed |
Page 169
Paragraph 1 |
Two Typos:
... problem of having to support customers on two releases by putting
some developers to work on the old release while others developers
worked in parallel on the new relese.
|
Anonymous |
May 14, 2009 |
| Printed |
Page 223
1/3 |
On this an example is given in which a user directory (./team/sue) is placed under
the Unix Standard Release (/usr) tree. Directory /usr is reserved for system
components. User directories belongs under /home (/home/team/sue).
While just a nit, this error indicates that the writer doesn't use or understand the
UNIX/Linux environment.
|
Anonymous |
|
| Printed |
Page 295
end of section #3 from previous page; paragraph above section #4 |
The author suggests that changes 10033 & 10029 cannot be released because they are
tainted by change 10034 which has an open job (job001426) attached to it. But both
changes 10029 & 10033 happened chronologically before 10034 and have no open jobs
against them, so I don't understand why they cannot be released. There was nothing
in the text to suggest that job001420 (attached to changes 10029 & 10033) has a
dependency on job001426 which might make it undesirable to release changes for
job001420 without also including job001426.
So, either changes 10029 & 10033 can be released given the description of the
scenario OR there needs to be a better explanation as to why they cannot be released.
|
Anonymous |
|