Re: [p4] Merging one changelist into multiple locations
Sambwise <[email protected]> Thu, 26 Apr 2018 23:25:01 -0700
| Newsgroups | gmane.comp.version-control.perforce |
|---|---|
| Message-ID | <[email protected]> |
Posted on behalf of forum user 'Sambwise'. [https://forums.perforce.com/index.php?app=forums&module=forums§ion=findpost&pid=23369] p4rfong, on 2018/04/26 18:27:21 UTC, said: > You can use "ditto" mappings where a file is mapped to multiple locations. So one location would be actual and the others would be linked to the original location. > See > https://www.perforce.com/perforce/doc.current/manuals/p4guide/index.html#P4Guide/configuration.workspace_view.one-to-many.html?Highlight=mappings > > Major new functionality in 2016.1 > #1357095 (Bug #5897) * ** > Ditto (&) mappings are now supported in client views. > These allow a client to map files from the depot into multiple > locations in the workspace in a one-to-many fashion. > Files mapped with this flag are read-only, and may not be open by > 'p4 edit', etc. The same files may also be normally mapped, allowing > a single copy of the file in the workspace to be openable. > Each sync'ed copy of the same file has it's own have record, and so > can be sync'ed to a different revision from the other copies of the > same file. To sync a specific copy of a file, you must specify the > path in client syntax. > Existing clients will be able to sync files mapped with ditto > mappings. In order for 'p4 fstat' to show details about ditto mapped > files, p4 must either be updated or the '-zexpandAndmaps' global > flag must be provided. > Last I checked those don't work in branch views (although I might be out of date)... -- Please click here to see the post in its original format: http://forums.perforce.com/index.php?/topic/5707-merging-one-changelist-into-multiple-locations _______________________________________________ perforce-user mailing list - [email protected] http://maillist.perforce.com/mailman/listinfo/perforce-user