4
Finding obsolete branches
5
-------------------------
7
If you use feature branching for developing each fix
8
and enhancement separately, you may have several old
9
branches that are no longer required. In many cases,
10
the relevant changes may now be merged into trunk.
11
In other cases, a branch may be obsolete thanks to
12
another change made by yourself or others.
14
When checking for an obsolete branch, there are three
15
things in particular to confirm:
17
1. The working tree has no in-progress changes.
19
2. The working tree has no shelved changes.
21
3. Any locally committed revisions have been merged
22
into the parent branch.
24
After changing into the root of a branch, the commands
25
to check these things respectively are::
29
bzr missing --mine-only
31
If your branches are stored in a shared repository locally,
32
you may find the *Local Changes* tab in Bazaar Explorer's
33
repository view helpful here (revision 159 or later) as it
34
shows a summary of these things, excluding the shelve information
35
currently, for each branch as you select it.
added
removed
doc/en/upgrade-guide/tips_and_tricks.txt
