Re: [p4] unshelve -branch failing with "No target files in both client and branch view"
Sambwise <[email protected]>
| Newsgroups | gmane.comp.version-control.perforce |
|---|---|
| Message-ID | <[email protected]> |
Posted on behalf of forum user 'Sambwise'. Yeah, branch specs are pretty confusingly named being that they aren't actually one-to-one with branches. This has been confusing people for twenty years. :) One really positive thing streams did for making Perforce branching easier to understand is that each "stream" spec actually represents one stream (branch), and the branch views associating them are computed automatically. Quote > unshelve the changes in CL# 1234 which you will find in the area identified as the "from" part of the mapping It works in the other direction too; if the shelved files are on the right hand side of the mapping, "unshelve -b" just maps them to the left side and opens the files there. (It's similar to using the "-s" flag on integrate -- since you specified the source explicitly, in this case via the shelved change, Perforce can infer the direction in which to apply the mapping.) -- Please click here to see the post in its original format: http://forums.perforce.com/index.php?/topic/5602-unshelve-branch-failing-with-no-target-files-in-both-client-and-branch-view _______________________________________________ perforce-user mailing list - [email protected] http://maillist.perforce.com/mailman/listinfo/perforce-user