Comment 2 for bug 1613681
Revision history for this message
| Alistair Coles (alistair-coles) wrote | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I would suggest that the proposed server behaviour is undesirable. Yes, there may be use cases where the end-result is as proposed, and they may be the common cases. But there may also be use cases where the intention is that the synced manifest in the target container continues to point to segments in the source container. It would be dangerous to assume the intent of the user and start re-writing user-generated metadata when syncing objects.
Although it is not a *great* experience, I am inclined to think that it's best to educate the user as to what to expect from container sync through better documentation.