11
Look at somebody else's tree or email submissions.
13
Looking at the patch alone may not be enough; we might need to apply
14
it to a tree, build it and see if we like it.
22
Clearcase allows you to put all new development onto branches that are
25
Can we detect which development branches have unmerged changes? Can
26
we dispose of those branches?
33
Get rid of any changes that have been merged in but not yet
34
committed. Shouldn't this just be ``bzr revert``?
38
cross damage problem with PQM
39
=============================
45
undo some uncommitted changes
46
=============================
48
If you've made some changes and don't want them::
52
This stores them as a changeset in a directory that you can move
53
around. You can set a name for it::
55
baz undo --name blargh-refactor foo.c bar.c
62
move some in-progress changes onto a local branch
63
=================================================
65
This is useful if we decide some changes on a bound branch should be
66
done on a separate branch; in particular people will want to do this
67
if they want to work in only one subdirectory of a complex config.
69
Possibly this should be the default with no arguments for ``bzr
70
branch``. Or possibly there should be a separate ``bzr unbind``.
77
I'm working on a Python project, which leaves bytecode files in the
87
OK, there is some danger here that people always forget to quote globs
88
on the command line but maybe this will be enough.
90
Maybe take only one at a time so that we can catch unquoted globs like
93
baz ignore *.pyc # wrong!
95
If they do this, they see all '* added foo.pyc to .arch-inventory';
96
then they can do this to get back::
98
baz undo .arch-inventory
100
This is potentially much more pleasant than Subversion.
107
I accidentally commit some files with the wrong message and want to
112
% bzr commit -s 'fix foo'
118
% bzr commit -s 'fix foo and bar'
120
This fix should be done as soon as possible, before anything else
121
depends on the change.
128
Come in Monday morning; can't remember what you were doing.
130
* log; look at what was committed
131
* diff against upstream, or recent revisions
added
removed
doc/use-cases.txt
