- Committer: John Arbash Meinel
- Date: 2007-04-10 18:30:32 UTC
- Revision ID: john@arbash-meinel.com-20070410183032-rw4d3kpb8f9cesfw
We don't need to extract ancestry_b until we after we've checked for existence.
It seems to make sense to check 'b in ancestry_a' first, though we might consider checking
a in ancestry_b first.
b in a is merging something which has already been merged.
a in b is merging something which has merged you.
And 'a in b' may actually be more common.
The timing difference is fairly small, though.
It seems to make sense to check 'b in ancestry_a' first, though we might consider checking
a in ancestry_b first.
b in a is merging something which has already been merged.
a in b is merging something which has merged you.
And 'a in b' may actually be more common.
The timing difference is fairly small, though.
| Filename | Latest Rev | Last Changed | Committer | Comment | Size | ||
|---|---|---|---|---|---|---|---|
 ..
|
|||||||
__init__.py |
2024.2.3 | 18 years ago | John Arbash Meinel | Move out export tests from test_too_much, refactor | 4.8 KB |
|
|
|
dir_exporter.py |
1852.15.4 | 18 years ago | Robert Collins | Merge bzr.dev. | 1.5 KB |
|
|
|
tar_exporter.py |
1852.6.6 | 18 years ago | Robert Collins | Finish updating iter_entries change to make all te | 1.9 KB |
|
|
|
zip_exporter.py |
1852.16.3 | 18 years ago | Robert Collins | Merge bzr.dev | 3.3 KB |
|
|