4083
4083
created as above. Directories containing unknown files will not be
4086
The working tree contains a list of pending merged revisions, which will
4087
be included as parents in the next commit. Normally, revert clears that
4088
list as well as reverting the files. If any files are specified, revert
4089
leaves the pending merge list alone and reverts only the files. Use "bzr
4090
revert ." in the tree root to revert all files but keep the merge record,
4091
and "bzr revert --forget-merges" to clear the pending merge list without
4086
The working tree contains a list of revisions that have been merged but
4087
not yet committed. These revisions will be included as additional parents
4088
of the next commit. Normally, using revert clears that list as well as
4089
reverting the files. If any files are specified, revert leaves the list
4090
of uncommitted merges alone and reverts only the files. Use ``bzr revert
4091
.`` in the tree root to revert all files but keep the recorded merges,
4092
and ``bzr revert --forget-merges`` to clear the pending merge list without
4092
4093
reverting any files.
4094
Using "bzr revert --forget-merges", it is possible to apply the changes
4095
from an arbitrary merge as a single revision. To do this, perform the
4096
merge as desired. Then doing revert with the "--forget-merges" option will
4097
keep the content of the tree as it was, but it will clear the list of
4098
pending merges. The next commit will then contain all of the changes that
4099
would have been in the merge, but without any mention of the other parent
4100
revisions. Because this technique forgets where these changes originated,
4101
it may cause additional conflicts on later merges involving the source and
4095
Using "bzr revert --forget-merges", it is possible to apply all of the
4096
changes from a branch in a single revision. To do this, perform the merge
4097
as desired. Then doing revert with the "--forget-merges" option will keep
4098
the content of the tree as it was, but it will clear the list of pending
4099
merges. The next commit will then contain all of the changes that are
4100
present in the other branch, but without any other parent revisions.
4101
Because this technique forgets where these changes originated, it may
4102
cause additional conflicts on later merges involving the same source and
4102
4103
target branches.