19 messages in com.perforce.perforce-userPerforce wish list
FromSent OnAttachments
TomB...@ebc.ericsson.se19 Jan 1999 23:43 
BobA...@weblogic.com19 Jan 1999 23:57 
Paul...@zergo.com20 Jan 1999 01:10 
Sand...@hmmh.com20 Jan 1999 06:13 
Paul...@zergo.com20 Jan 1999 06:32 
chri...@natinst.comchris.bartz20 Jan 1999 08:12 
Brad...@enteract.com20 Jan 1999 08:19 
Andr...@placeware.com20 Jan 1999 08:52 
Scot...@seanet.com20 Jan 1999 10:36 
Stev...@qualcomm.com20 Jan 1999 10:57 
Scot...@seanet.com20 Jan 1999 11:18 
Davi...@home.chat.net20 Jan 1999 11:35 
Andr...@placeware.com20 Jan 1999 11:44 
Robe...@scrap.de21 Jan 1999 00:41 
Scot...@seanet.com21 Jan 1999 09:45 
Timo...@ftlsol.com21 Jan 1999 13:12 
Robe...@scrap.de21 Jan 1999 22:49 
Scot...@seanet.com22 Jan 1999 11:56 
Robe...@scrap.de24 Jan 1999 08:06 
Subject:Perforce wish list
From:Paul...@zergo.com (Paul@zergo.com)
Date:01/20/1999 06:32:05 AM
List:com.perforce.perforce-user

In addition to all of the above (earlier mails). I'd like to add that client specs should have some form of versioning and an easier way to adopt them.

We use a common directory structure which works fine for everything except Java. (Unlike most languages, Java cares about the heirarchy it's built under.)

So we have multi-line client specs that need to be used by multiple users and also are important to the delivered configuration of the products.

At the moment, we're using p4 client -o > viewTemplate.txt and then checking in viewTemplate.txt so that it can be recovered later.

But it would be much easier if p4 supported versioning and sharing client specs directly.

Paul.