Date: Mon, 7 Apr 2008 13:56:40 -0400 From: John Baldwin <jhb@freebsd.org> To: Mike Meyer <mwm@mired.org> Cc: freebsd-hackers@freebsd.org, Ed Schouten <ed@80386.nl> Subject: Re: Perforce and `p4 diff2' against the origin Message-ID: <200804071356.41181.jhb@freebsd.org> In-Reply-To: <20080407124300.5195e299@mbook-fbsd> References: <20080405145038.GE5934@hoeg.nl> <200804071039.07210.jhb@freebsd.org> <20080407124300.5195e299@mbook-fbsd>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 07 April 2008 12:43:00 pm Mike Meyer wrote: > On Mon, 7 Apr 2008 10:39:07 -0400 John Baldwin <jhb@freebsd.org> wrote: > > > On Saturday 05 April 2008 10:50:38 am Ed Schouten wrote: > > > Hello everyone, > > > > > > Because my mpsafetty project in Perforce is going quite well, I'm > > > considering running some kind of cron job to generate nightly diffs, so > > > other people (interested friends, colleagues and others) to test my > > > work. > > > > > > I've read `p4 help diff2' and it seems you can run the following > > > command: > > > > > > p4 diff2 -b mpsafetty > > > > > > Unfortunately this command just does a braindead diff against the latest > > > FreeBSD vendor source, which is not useful in my case. I just want it to > > > generate a diff against the version I integrated. > > > > > > Is it possible to do this with Perforce? > > Then you can use p4 changes on your branch and find the last IFC and use that > > diff like so: > > > > p4 diff2 -u -b mybranch @12345 #head > > > > I have a script to look in p4 changes of the branch to find the last IFC > > commit and figure out the '12345' part automatically like so: > > > Perforce has facilities designed specifically to support this kind of > thing - counters and the "review" command. You can find a brief > description plus a link to the perforce-standard review daemon here: > > http://www.perforce.com/perforce/loadsupp.html#daemon > > It's designed to send email to perforce user. > > Actually, something similar ought to be running on the repository > already. If so, and you're not using it, you can 'cheat' by setting up > the mail list you want and pointing your p4 user Email field at that, > along with the appropriate Reviews setting for yourself. This is not for e-mails for individual submits. This for generating a cumulative patch of all the differences in one branch relative to the parent. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200804071356.41181.jhb>