[p4] How do YOU identify the code set for a release?

[Steve Williams]

Rick Macdonald wrote:
> I was wondering how you were going to build it if it wasn't on disk...
>
> If a sync of 10's of gigabytes of source code takes half an hour, 
> doesn't the build run until the next day anyway?
>   

The tens of gigabytes includes game data files as well as source code.  
The build itself generally takes around an hour or two.


> I did it in a csh script once with this:
>
> p4 change -o | sed "s~<enter description here>~Creating release branch 
> $relnum.~1"| p4 submit -i
>
> Are you looking for help to dissuade the change to Perforce, or for help 
> in streamlining the process using Perforce?
>
>   

I'm still learning a lot about Perforce, so this thread has actually 
been useful in many respects.  The pool of Perforce knowledge in the 
company is quite limited, so I'm still trying to learn "the Perforce 
way" of working.

-- 
Sly



This message and its attachments may contain legally privileged or confidential information. This message is intended for the use of the individual or entity to which it is addressed. If you are not the addressee indicated in this message, or the employee or agent responsible for delivering the message to the intended recipient, you may not copy or deliver this message or its attachments to anyone. Rather, you should permanently delete this message and its attachments and kindly notify the sender by reply e-mail. Any content of this message and its attachments, which does not relate to the official business of the sending company must be taken not to have been sent or endorsed by the sending company or any of its related entities. No warranty is made that the e-mail or attachment(s) are free from computer virus or other defect.