Date: Mon, 07 Apr 2008 14:58:52 -0700 From: Julian Elischer <julian@elischer.org> To: Ed Schouten <ed@80386.nl> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: Perforce and `p4 diff2' against the origin Message-ID: <47FA991C.80704@elischer.org> In-Reply-To: <20080407200225.GQ5934@hoeg.nl> References: <20080405145038.GE5934@hoeg.nl> <200804071039.07210.jhb@freebsd.org> <20080407200225.GQ5934@hoeg.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Ed Schouten wrote: > * 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? >> One option is to create a label and sync it each time you do an integ. I do >> this for projects/smpng. Then I can do: >> >> p4 diff2 -u -b smpng @smpng_base #head > > I just tried this and just wanted to say it works great. This method is The two scripts I mentioned do exactly this. (but easier on the eyes.) >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47FA991C.80704>