← Back to branch summary

~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

Viewing changes to doc/developers/implementation-notes.txt

  • Committer: John Arbash Meinel
  • Date: 2007-04-10 18:30:32 UTC
  • mto: This revision was merged to the branch mainline in revision 2403.
  • 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.

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/developers/implementation-notes.txt
1
 
Implementation notes
2
 
====================
3
 
 
4
 
.. toctree::
5
 
   :hidden:
6
 
 
7
 
   btree_index_prefetch
8
 
   last-modified
9
 
   content-filtering
10
 
   lca_tree_merging
11
 
 
12
 
 
13
 
* `BTree Index Prefetch <btree_index_prefetch.html>`_ |--| How bzr decides
14
 
  to pre-read extra nodes in the btree index.
15
 
 
16
 
* `Computing last_modified values <last-modified.html>`_ for inventory
17
 
  entries
18
 
 
19
 
* `Content filtering <content-filtering.html>`_
20
 
 
21
 
* `LCA Tree Merging <lca_tree_merging.html>`_ |--| Merging tree-shape when
22
 
  there is not a single unique ancestor (criss-cross merge).
23
 
 
24
 
 
25
 
.. |--| unicode:: U+2014
26
 
 
27
 
..
28
 
   vim: ft=rst tw=74 ai