© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Hi
I understand your point. Maybe the upload plugin should, by default, mirror what happens for instance when one bzr branch is merged into another -- in the case where the source branch has had a file bzr removed and the target branch has had the same file manually removed.
I'm not sure if --force would be the correct verb to describe the process - maybe "--ignore" to sliently ignore upload errors ?
Finally, the workaround described is not really valid. The point of the plugin is to upload changed files - if I wanted to upload the entire tree every time, then I'd use plain old FTP. If I have a 300MB website to upload to a remote server but only 30kb of changes, that's not an efficient process.
I'd suggest implementing the --ignore flag would solve the issue in hand and provide a generic way of ignoring upload errors. I'm just unsure at the moment of the scope of an "--ignore" - it may ignore things that really ought to cause an upload failure.