1 message in com.perforce.perforce-userRestricting viewed information
FromSent OnAttachments
Scot...@maplesoft.com06 Apr 1999 05:51 
Subject:Restricting viewed information
From:Scot...@maplesoft.com (Scot@maplesoft.com)
Date:04/06/1999 05:51:14 AM
List:com.perforce.perforce-user

We are just getting started with Perforce and I have a few questions:

1. We will have many projects working in the same depot, each corresponding to a different product or product component. Each of the projects are worked on by a different team of developers. How do I restrict what is viewable by a particular team in terms of branchspecs, labelspecs, clientspecs, etc? For example, I'm a developer on TeamA and want to look at the list of branches. In P4Win I select view branches. Will I always see all branchspecs in the depot? I'd rather just see the branchspecs that are relevant to the clientview I am currently using.

2. To do branching, both the source and destination locations need to be in my clientspec. Is there a way of doing a branch without having the destination tree local on my machine?

3. Is there a way of seeing what changelists have been made to a source in a branchspec that have yet to be propagated to the destination? As well, I would like to promote between source and destinations of a branchspec on a changelist level, not file level.

4. Suggestion for P4Win: For a particular changelist, the context menu should contain a resolve sub-menu that will go through each of the files involved in the changelist and resolve (auto / interactive / whatever)

--- Scotte

------ Scotte Zinn Manager, GUI Development Waterloo Maple Inc mailto:szinn at maplesoft.com http://www.maplesoft.com