|
6
by mbp at sourcefrog
import all docs from arch |
1 |
Bitkeeper compared to Arch |
2 |
========================== |
|
3 |
||
4 |
BK has a default GUI, which is good, but it's ugly and not all that |
|
5 |
friendly to the new user. It does pay attention to allowing quick |
|
6 |
keyboard navigation. |
|
7 |
||
8 |
The tool itself is also a bit unfriendly in terms of emitting a lot of |
|
|
254
by Martin Pool
- Doc cleanups from Magnus Therning |
9 |
noise messages and having lots of weird commands. |
|
6
by mbp at sourcefrog
import all docs from arch |
10 |
|
11 |
Bitkeeper always requires both per-file and per-changeset commands. |
|
12 |
It seems bad to always require this; at most per-file messages should |
|
13 |
be optional. Are they really the best option? |
|
14 |
||
15 |
Claimed to have extremely space-efficient storage, keeping 19 years of |
|
16 |
history in slightly more than twice the size of the working copy. |
|
17 |
||
18 |
Hashes: does Baz always have these even without signing? It really |
|
19 |
should. |
|
20 |
||
21 |
Fine-grained event triggers, pre- and post-event. |
|
22 |
||
23 |
Can remotely find status of a tree, e.g. parent, number of comitters, |
|
24 |
versioned files, extras, modified, etc. |