I don't want to add a mapping between local names and remote names.
I think what you want here may be better addressed by having a nested tree that you will then upload as a whole where you want.
We need nested tree to be supported by bzr for that.
If you still want to upload your tree partially but keeping the same relative paths
locally and remotely, then, as Martin said, a mix of .bzr-upload.ignore and an
explicit list of files to upload can address that (both features are still missing though :-/)
I don't want to add a mapping between local names and remote names.
I think what you want here may be better addressed by having a nested tree that you will then upload as a whole where you want.
We need nested tree to be supported by bzr for that.
If you still want to upload your tree partially but keeping the same relative paths
locally and remotely, then, as Martin said, a mix of .bzr-upload.ignore and an
explicit list of files to upload can address that (both features are still missing though :-/)