Re: [p4] referring to files from another depot

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

Thanks for your reply.  As mentioned above, I'm new to Perforce,
so would you mind clarifying what you mean by "mapping files into
client"?

The two mentioned depots are indeed on the same Perforce
server.  Please note also that the other depot has number of
sub-directories, and my depot directory structure has same sub-directories, when
needed (when I'm not using files from some sub-directory of other depot,
I'm not creating corresponding sub-directory).  Furthermore, most
of the time I'm only using some of files from given sub-directory from this
other depot.  As mentioned above, most of the files will stay
unchanged, and in some of them I'll add some small changes.  On
top of all of that, I have some files and sub-directories of my own in my
project, but these are completely separated from ones from the other project.

What I'd like to be able is to sync changes from that other project (again:
my changes won't go in the other direction).  So, speaking in SVN
terminology, it would be like that I've created a branch, but only with a
part of the trunk involved, and I want to merge changes from trunk from time to
time, but I actually will never merge my branch back in the
trunk.  (Sorry for using terminology of that other CVS, but I hope it
helps to explain what I want to achieve with Perforce, if possible).

Thanks.



--
Please click here to see the post in its original format:
  http://forums.perforce.com/index.php?/topic/5456-referring-to-files-from-another-depot
_______________________________________________
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.