9 messages in com.perforce.perforce-userfinding out what's changed since...
FromSent OnAttachments
Dave...@vignette.com05 Oct 1998 12:44 
Davi...@home.chat.net05 Oct 1998 13:25 
Long...@mindq.com05 Oct 1998 13:29 
Dave...@vignette.com05 Oct 1998 14:20 
Jerr...@esd.sgi.com05 Oct 1998 15:18 
J.Bo...@hotmail.com05 Oct 1998 15:50 
Davi...@home.chat.net05 Oct 1998 16:26 
EdMa...@wrq.com05 Oct 1998 17:46 
Dave...@vignette.com05 Oct 1998 19:15 
Subject:finding out what's changed since...
From:J.Bo...@hotmail.com (J.Bo@hotmail.com)
Date:10/05/1998 03:50:10 PM
List:com.perforce.perforce-user

<html> <font size=3>At 01:25 PM 10/5/98 -0700, David Jeske wrote:<br> &gt;Or, for the utmost in trackability, I would have the daily build start<br> &gt;by branching _every night_. That way, you could generate the<br> &gt;differences between two 'daily build snapshots' by asking for the<br> &gt;changes between two branches.<br> <br> Branches might be inexpensive, but isn't this what labels are for?<br> <br> In fact, you can even run &quot;p4 changes @label1, at label2&quot; in the most<br> recent version of the product....<br> <br> -Jeff Bowles<br> <br> ps. I strongly believe that, whether you use the same Perforce client<br> each night for a build or use a different client, you should always<br> start with an empty client area so that remnants of last night's build<br> *never* affect tonight's build.</font></html>