Comment 2 for bug 269095

As far as I understand the data structures of bzr, it might not be easy to directly implement a historic relationship between two repository objects with different file ids.

However, the problem might be solved indirectly by simply adding another metadata item to the commit log entry which describes the parent file-ids of all forked file system objects for this check-in.

Then "bzr cp" would be very much like "bzr add", only that a metadata record is also added which describes the parent file-id of the newly copied file.

This should not require any dramatic changes to the repository data structures, but it will at least record the per-file inheritance relationships for a later time to come when other bzr commands will actually make use of this new metadata item.

At least the information will no longer be lost!