Re: [p4] Issue creating a 2nd depot on server. File(s) not under client view.

P4Reg <[email protected]>
Newsgroups gmane.comp.version-control.perforce
Message-ID <[email protected]>
Posted on behalf of forum user 'P4Reg'.

If you have created the new depot already it sounds like you might just need to
create the top level workspace root folder and cpy the files you want to add
under that location and add them. 

For example I just created a new depot called reg1 and created a new client to
just map that depot in the client view. The client root
is  C:\Users\Reg\Perforce\reg_reg-win8_5714 which does not exist
yet  (normally for a populated depot it gets automatically created the
first time the workspace is sync'd so this situation only really happens
with a new, empty depot)


So from P4V, Connection->Edit current connection, for whatever folder you
have set for your workspace root, create it manually (e.g. from windows
explorer) 
You should now be able to copy the files you want to add under that workspace
root folder in explorer and add them in P4V (you may need to refresh the P4V
Workspace tree if you can't see them right after copying them to the
workspace).

Where they go in the depot depends on your view mapping, for example my view
mapping is

//newdepot/... //reg_reg-win8_5714/newdepot/...

So if I copy a file under the client root in the relative location I want to put
it in the depot , for example:

C:\Users\Reg\Perforce\reg_reg-win8_5714\newdepot\folder1\file.txt

When I add it will be located at //newdepot/folder1/file.txt in the depot

Hope that makes sense



--
Please click here to see the post in its original format:
  http://forums.perforce.com/index.php?/topic/5513-issue-creating-a-2nd-depot-on-server-files-not-under-client-view
_______________________________________________
perforce-user mailing list  -  [email protected]
http://maillist.perforce.com/mailman/listinfo/perforce-user
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.