[p4] perforce-user Digest, Vol 34, Issue 5

[Toby Allen]

Sam Clegg Wrote 
>>Yuck.  Nothing against your shell scripting, but p4 should make this
>>common task simpler than the above.

If you are doing this kind of thing, it may be much better to set up a
system of branches that can 
Be used to review code against rather than passing around numbers of
non-submitted changelists.  One of the
Really big benefits of perforce is that is makes branching so easy that
there is no reason not to submit 
Code even if you submit it only against your own personal branch.

Take a look at settin up a system where your developers will submit
against a dev branch, they then pass the submitted
Changelist number for someone to review, if it passes it is integrated
into the mainline.  This does exactly what
You want but in the way that Perforce intends.

Toby Allen
QUMAS


On Mon, 2007-10-08 at 15:59 +0100, Tony Sweeney wrote:
> Roy Smith wrote:
> > Yes, but what I'm trying to figure out is how to make it suppress  
> > things that are not on the default changelist, so I can see exactly

> > what's going to get submitted when I do "p4 submit".
> >   
> Roy,
> 
> this (or something like it) should do what you want on UNIX derived
systems:
> 
>     p4 opened -c default | grep ' - edit default change ' | sed -e 
> 's/#.*$//' | p4 -x - diff

Yuck.  Nothing against your shell scripting, but p4 should make this
common task simpler than the above.

> I could have sworn 'p4 diff' implemented this directly, but no.

I've been wishing that this was built-in for a long time.  This is
essential for passing code around for reviews when you have many open
changelists.

Why can't "p4 describe" show the diffs of pending changlists when
running on the machine where the changes exist?

-- 
sam clegg
sam at ideaworks3d.com 




********************************************************

This email message is for the sole use of the intended recipient(s) and may contain confidential and/or privileged information. Any unauthorized review, use, disclosure, printing, copying or distribution is prohibited.  If you are not, or believe you are not, the intended recipient, please contact our systems administrator immediately at postmaster at qumas.com and destroy all copies of the original message and any attachments.

Any views or opinions presented are solely those of the author and do not necessarily represent those of QUMAS.

QUMAS has a virus detection policy but cannot accept responsibility for any loss or damage arising from the opening or use of this email and/or attachments.


********************************************************