[p4] List of Changed files in a Branch

J. Bowles jab at piccoloeng.com
Thu Aug 1 07:52:48 PDT 2002


At 07:33 AM 7/31/2002 +0000, Mohan  Janam wrote:
>I want the list of all the files changed in a branch after branching happened.
>
>Or shall I have to write a scripts in PERL to retrieve such files.

There's always the command:
         p4 files //depot/release1/... at 12346, at now
where change 12345 (note, that's one before the number in the command
above) is the one that created the branch.

This means, "show me all things that have been submitted to this
pathname from changelist 12346 to the present, including changelist
12346 itself."  While this will not tell you every single revision for the
files submitted more than once during this period, it'll give you the
filename info you desire.

By restricting it with both a range and the pathname, you get the list
of things that happened there but nowhere else. (If you didn't give the
range, it'll give you more information on earlier revisions. I won't type
in examples of that into this email for fear of giving too much information
that might confuse the examples, above.)

---------

Now, the rest of my question: what are you trying to do? I mean, in
a high-level description.

I mean, are you trying to figure out what to pull down into a build
area to rebuild? ("p4 sync -n" will give more useful information.)
Produce a report of changes that might need to go into an eventual
patch build? (The "p4 files" command, above, will be helpful for that.
Still, you might want to adopt an "it's not put into the branch until
actually ready to build the patch" model. That's your choice, and
so long as you are painfully consistent every time, practically any
choice of yours is the "right" one.)

         -Jeff Bowles




More information about the perforce-user mailing list