5 messages in com.perforce.perforce-user[p4] p4 changes question...| From | Sent On | Attachments |
|---|---|---|
| Andrew Nguyen | 13 Feb 2003 17:59 | |
| Vinny Murphy | 13 Feb 2003 19:56 | |
| Andrew Nguyen | 14 Feb 2003 14:58 | |
| Dave Rehring | 14 Feb 2003 15:30 | |
| Chuck Soper | 19 Feb 2003 09:17 |
| Subject: | [p4] p4 changes question...![]() |
|---|---|
| From: | Andrew Nguyen (ANgu...@oblix.com) |
| Date: | 02/13/2003 05:59:05 PM |
| List: | com.perforce.perforce-user |
Hi Vinny,
p4 changes "@>NP52Access_FCS1.0,@<=NP52Access_FCS1.2a"
Is there anything wrong with the command above? the command stayed put for
awhile, then returned empty. It doesn't like the single quote, so I use double
quote.
Thanks, -Andy
-----Original Message----- From: Vinny Murphy [mailto:vmurphy at cisco.com] Sent: Friday, January 31, 2003 5:50 PM To: perforce-user at perforce.com Subject: [p4] p4 changes question...
Hi,
I have been using the undocumented revision changes to get information about the changes between two labels. Here is what I do:
p4 changes '@>label_one,@<=label_two' where label_one is one build label and label_two is the next build on the same branch.
This works great!
However, if I change it to be:
p4 changes '@>label_one,@<label_two' I now get a few of the change lists between the two labels and, at that, they aren't even contiguous. Anyone have any theories or explanations for this behavior?
-- Vinny
_______________________________________________ perforce-user mailing list - perforce-user at perforce.com http://maillist.perforce.com/mailman/listinfo/perforce-user




