Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Sounds like it should be easier than I have found; which is
p4 change -so <changenum> | grep Client |sed/awk magic| p4 client -o <userclient> | grep -1 View: | tail -1 | <sed/awk magic for depot path>
-Chris
Perforce branches are normally just identified by a location in the directory structure (unless you’re using streams). If you know the convention your company uses, it’s pretty easy to spot, e.g.:
//depot/project/main/src/foo.cYou can also use the Revision Graph in P4V to see the branching history.