3
* 'shelf' command with subcommands like 'list', to show what shelves there
4
are, with any associated message etc. Steal code from log?
6
* Multiple shelves, use 'bzr shelf switch' (?) to choose between them.
7
This is quilt like stuff, need to think more about it - track unshelved
8
changes? Do they get reshelved when you switch? Probably not.
10
3
* Shelving of committed changes. Three modes (config option?), either uncommit
11
4
the committed changes (changing history) or apply the inverse diff (messy,
12
5
but not so scary), or prompt.
14
* Messages for each patch on the shelf. User specifiable, use commit code.
15
If nothing specified it's:
16
"Uncommitted changes shelved on YYYY-MM-DD at HH:MM:SS by user@host"
7
* shelf commands that operate on the shelved patches should assume the top
8
most (highest numbered) patch if no argument is given, eg. show/del.
18
For shelving committed changes, use some (all) of the commit message.
10
* shelf del should create backups.
22
* Use exceptions in UserInteractor rather than global booleans.
24
14
* Interact with bzr at a lower level, ie. not by parsing diffs. Will probably
25
15
require changes to bzr core, or can we just use a delta object directly?