I simply don't know anything of BZR internals... I am not even sure your post concerns me.
I take the opportunity, however, to summarize the use case:
From a functional point of view (I, dumb user, if you prefer ;-) ):
- I've a working copy of a remote branch
- I've already worked a bit on a task 'T'
- a new task 'P' with higher priority arrives and I want to work on it, without losing the work already done for task 'T'
- I don't want to reconfigure all my dev tools to work on 'P' on another working copy of the remote branch (as I know there is 'bzr shelve' for that)
- I expect 'bzr shelve' to allow me to switch my working copy by keeping my currently unfinished work for task 'T' on the shelve
- I understand that BZR requires that I 'bzr add' new files/folders before shelving them, to distinguish them from garbage and generated stuff
- I can't do that if my work implies the creation of files in a new folder which has been 'bzr add'-ed without having been committed locally.
Quoting official BZR documentation about 'bzr shelve':
Purpose: Temporarily set aside some changes from the current tree.
I guess I am not expecting abilities not advertised by BZR.
I simply don't know anything of BZR internals... I am not even sure your post concerns me.
I take the opportunity, however, to summarize the use case:
From a functional point of view (I, dumb user, if you prefer ;-) ):
- I've a working copy of a remote branch
- I've already worked a bit on a task 'T'
- a new task 'P' with higher priority arrives and I want to work on it, without losing the work already done for task 'T'
- I don't want to reconfigure all my dev tools to work on 'P' on another working copy of the remote branch (as I know there is 'bzr shelve' for that)
- I expect 'bzr shelve' to allow me to switch my working copy by keeping my currently unfinished work for task 'T' on the shelve
- I understand that BZR requires that I 'bzr add' new files/folders before shelving them, to distinguish them from garbage and generated stuff
- I can't do that if my work implies the creation of files in a new folder which has been 'bzr add'-ed without having been committed locally.
Quoting official BZR documentation about 'bzr shelve':
Purpose: Temporarily set aside some changes from the current tree.
I guess I am not expecting abilities not advertised by BZR.