[p4] Returned mail: User unknown - William Wishon - com.perforce.perforce-user

3 messages in com.perforce.perforce-user[p4] Returned mail: User unknown

From	Sent On	Attachments
Viktor Haag	24 Jan 2000 14:47
Yariv Sheizaf	24 Jan 2000 23:07
William Wishon	25 Jan 2000 08:45	.pl

Subject:	[p4] Returned mail: User unknown
From:	William Wishon (bill...@dii.com)
Date:	01/25/2000 08:45:02 AM
List:	com.perforce.perforce-user
Attachments:	p4cico.pl - 3k

Here is a script I wrote in perl to do just that, p4cico.pl stands for checkin/checkout. Hope this helps.

-Bill

-----Original Message----- From: perf...@perforce.com [mailto:perforce-user-admin at perforce.com]On Behalf Of Yariv Sheizaf Sent: Monday, January 24, 2000 11:08 PM To: 'Viktor Haag' Cc: 'perforce-user at perforce.com' Subject: RE: [p4] Returned mail: User unknown

Viktor,

I agree with you that feature is required and could be very helpful. However, currently unavailable. The solution is to run a script which "p4 edit" all files in the just-submitted changelist (be careful - the changelist number is changed when submitted ! - You must take the number after submit action !).

Yariv

-----Original Message----- From: Viktor Haag [SMTP:vhaag at rim.net] Sent: Tue, January 25, 2000 12:48 AM To: Perforce Mailing List Subject: [p4] Returned mail: User unknown

As a write, I work in a fundamentally different manner from developers. Is there a way in Perforce to submit a set of changes to a repository, but still maintain a file open for editing? (i.e., in RCS, this would be ci -l)?

It seems kind of silly for me to checkout a dozen chapter files for editing, make changes to them, and then submit those changes, and check them all out again, when I'm the only one really working on the book (although I check in the changes, so that other people can see those changes by syncing their own work areas, those other people (the developers) won't be editing the files, only looking at them).