/brz/remove-bazaar

To get this branch, use:
bzr branch http://gegoxaren.bato24.eu/bzr/brz/remove-bazaar

« back to all changes in this revision

Viewing changes to doc/developers/annotate.txt

  • Committer: Vincent Ladeuil
  • Date: 2009-12-15 20:32:34 UTC
  • mto: (4905.1.1 integration)
  • mto: This revision was merged to the branch mainline in revision 4906.
  • Revision ID: v.ladeuil+lp@free.fr-20091215203234-d8br6xqfq6pec40z
Move the _warn_if_deprecated call from repo.__init__ to
repo.lock_{read,write} so that branch.lock_{read,write} can call it. This
makes it possible to access locations.conf and branch.conf.

* bzrlib/tests/blackbox/test_exceptions.py:
(TestDeprecationWarning): Test that the suppress_warning
configuration variable is taken into account.

* bzrlib/repository.py:
(Repository.__init__): Delete very old and obsolete
comments. Don't warn about deprecations yet.
(Repository.lock_write, Repository.lock_read): The repo is about
to be locked, check deprecation.
(Repository._warn_if_deprecated): Use the branch config if
available or the global one othewrwise and check for the
suppress_warning variable.

* bzrlib/remote.py:
(RemoteRepository._warn_if_deprecated): Nothing to do here. 

* bzrlib/repofmt/pack_repo.py:
(KnitPackRepository._warn_if_deprecated): Delegate to base class
if needed.

* bzrlib/branch.py:
(BzrBranch.lock_write, BzrBranch.lock_read): Check repo
deprecation.

* bzrlib/help_topics/en/configuration.txt:
Fix the variable name and its description.

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/developers/annotate.txt
 
1
Annotate
 
2
========
 
3
 
 
4
Broadly tries to ascribe parts of the tree state to individual commits.
 
5
 
 
6
There appear to be three basic ways of generating annotations:
 
7
 
 
8
If the annotation works by asking the storage layer for successive full texts
 
9
then the scaling of this will be proportional to the time to diff throughout
 
10
the history of thing being annotated.
 
11
 
 
12
If the annotation works by asking the storage layer for successive deltas
 
13
within the history of the thing being annotated we believe we can make it scale
 
14
broadly proportional to the depth of the tree of revisions of the annotated
 
15
object.
 
16
 
 
17
If the annotation works by combining cached annotations such that creating a
 
18
full text recreates annotations for it then it will scale with the cost of
 
19
obtaining that text.
 
20
 
 
21
Generally we want our current annotations but it would be nice to be able to do
 
22
whitespace annotations and potentially other diff based annotations.
 
23
 
 
24
Some things to think about:
 
25
 
 
26
 * Perhaps multiparent deltas would allow us to not store the cached
 
27
   annotations in each delta without losing performance or accuracy.
 
28