16
16
- symlinks in Arch trees are not handled (but can be skipped).
18
After more commits are made to the baz/arch branch, you can re-run baz2bzr
18
After more commits are made to the baz/arch branch, you can re-run baz-import
19
19
to import just those changes.
21
21
The conversion algorithm is still in flux, and old data may become invalid as
22
22
newer conversion functionality is introduced.
26
26
Uses rsync to copy a branch to a remote location. Remembers the last location
27
27
used. Will not push if
28
28
- there are unknown files
29
29
- there are uncommitted changes in the working tree.
30
30
These safeguards are intended to prevent dirty trees from being uploaded.
32
BZR-PULL (obsolete as of Bzr 0.5)
33
Uses rsync to get the latest changes from an upstream location. Remembers the
34
last location used. Will not pull if
35
- there are unknown files
36
- there are uncommitted changes
37
- there have been local commits
38
These safeguards are intended to prevent accidental data loss.
33
Output a version of the requested file that indicates which revision introduced
37
Temporarily put aside some changes, to restore them later. This can be useful
38
to separate two sets of changes, so that they can be committed separately.
41
Delete unknown (or, optionally, ignored) files, leaving versioned files
45
List files in the tree that have conflicts.
48
Mark conflicts as resolved, by deleting TREE, BASE and OTHER files.
51
Use dot (from Graphviz) to produce graphics of a tree's ancestry.
54
Scan this branch for missing ancestors, and attempt to retrieve them from
58
Use patch to apply a patch to this tree.
added
removed
README
