On 02/29/2012 03:52 AM, Greg Stein wrote: > This revision means that trunk is effectively a branch. It now has a > non-zero copy_id. > > Philip/Mike: will this pose us any problems? > > I asked Daniel, and he confirmed the new copy_id, but neither of us > know whether this is really a problem. Will it affect merges? I bet it > will affect --stop-on-copy in history tracing. etc etc.
Sheesh. It's not *supposed* to create any problems in the general sense, but yes, it just broke --stop-on-copy types of history tracing, introduced a historical gap (from 1295003 to 1295006), and will almost certainly be a nuisance. This is really not the correct way to revert changes. Not only does it cause the aforementioned issues, but in extreme cases it masks the details of the reversions, leaving others who have been tracking those changes made in trunk to wonder exactly what got reverted. (Probably should have had this conversation before this commit was made.) -- C. Michael Pilato <[email protected]> CollabNet <> www.collab.net <> Distributed Development On Demand
signature.asc
Description: OpenPGP digital signature
