[p4] Newbie Question
jab at pobox.com
Wed Jan 7 12:55:07 PST 2004
Budget three hours of time without any interruptions.
[At home is fine: run a copy of the two-user/two-workspace server on a
local Win/NT or Win/2000
machine for this. Just don't mix this experiment with your production
Find the tutorial, I believe it's chapter 3 or 4 of the online user
guide, and work through it.
The command-line version of the tutorial is actually easier to work
through, even if you don't
see the trees graphically.
Things to have at your fingertips:
1. Hard copy of user guide
2. A command that makes recursive directory listings to pass to "p4 -x
(That command on Unix is "find . -type f -print"; on Windows, it's
"dir /s /b /a-d".)
3. The afore-mentioned three hours, which is estimating on the
high-end. It should
be less time.
Avoid the command "p4 depot" (or "p4 depots") until you've used
Perforce for weeks/months.
It's a more advanced thing that you probably won't need, initially.
On Jan 7, 2004, at 12:23 PM, Brooke Gravitt wrote:
> I'm sure I'm just not quite understanding the semantics of Perforce,
> I'm a little confused about getting starting.
> I have, for example, 6 different codebases taken from 6 different
> in another CM tool. (CCC/Harvest, if anyone cares.)
> Perforce was started as "p4d -d -r e:\perforce" on Windows. I can
> to the server through the Windows Perforce GUI fine. I just can't see
> I have 6 different (_deep_) directory structures (containing thousands
> files) that I placed under the Perforce server's root directory (
> e:\perforce ), and then did:
> p4 depot test1
> p4 depot test6
> How do I make the files visible, and ready for versioning? Connecting
> the GUI gives an error, saying there are no files in the depot.
> Any help would be appreciated!!
> perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user