[p4] Re: integrate by changelist - Raja Aluri - com.perforce.perforce-user

4 messages in com.perforce.perforce-user[p4] Re: integrate by changelist

From	Sent On	Attachments
Raja Aluri	18 Aug 2003 19:56
Mike Castle	19 Aug 2003 00:16
Raja Aluri	19 Aug 2003 09:41
Mike Castle	20 Aug 2003 09:43

Subject:	[p4] Re: integrate by changelist
From:	Raja Aluri (RAl...@ariba.com)
Date:	08/19/2003 09:41:37 AM
List:	com.perforce.perforce-user

1) I want to get the last integrated change list, to generate the checkin notes for the integration, not for doing the integration itself. (Like this integration is a bunch of checkins on this branch to the other branch, so once in a while missing one or two change lists is OK) 2) I was trying to use p4 integrated, but that seems to be pretty slow and even then you have to do a lot of output parsing to figure out the right change list.

That's why I wanted to see, if anybody elase knows any tricks to find that the best way interms of spped and load on perforce server.

Raja

-----Original Message----- From: dalg...@ix.netcom.com [mailto:dalgoda at ix.netcom.com] Sent: Tuesday, August 19, 2003 12:17 AM To: perforce-user at perforce.com Subject: [p4] Re: integrate by changelist

In article <19A187F26DD4D311949F009027E28ACE16B6701B at mail.ariba.com>, Raja Aluri <RAluri at ariba.com> wrote:

Hi All, Is there any simple of way of finding out the last change list number or the version number that was integrated previously from a source branch into a target branch?

Unfortunately, this really doesn't make sense. After all, one can integrate a single change list, leaving 'holes' in the list of candidate change lists; so paying attention to the last change list number may not necessarily be appropriate.

Here is a bourne shell script I made up the other day that I use to list all change lists that are not integrated. Perhaps it could be of inspiration to you? (Note that it's about a week old, and I know there are some file name patterns that will screw it up.)

mrc

stle at dl-mcastle[00:12am]~(1001) cat bin/find-unmerged-changes #!/bin/sh p4 integ "$@" -n ... \ | sed -e 's+.* - delete from ++' -e 's+.* - integrate from ++' -e 's+.* | - branch/sync from ++' \

integ.out

grep ,# integ.out > comma.out cat integ.out \ | while read line ; do p4 changes -m1 "$line" done > changes.out cat comma.out \ | while read line; do p4 changes "$line" done >> changes.out sort changes.out | uniq > final.out #rm changes.out comma.out integ.out cat final.out mcastle at dl-mcastle[00:12am]~(1002)

I use this command from one of my larger client specs that have branches laid out in more or less depot order rather than traditional project order that we use most of the time around here.

mrc