← Back to branch summary

~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

Viewing changes to doc/requirements.txt

  • Committer: Martin Pool
  • Date: 2006-06-15 05:36:34 UTC
  • mto: This revision was merged to the branch mainline in revision 1797.
  • Revision ID: mbp@sourcefrog.net-20060615053634-4fd52ba691855659
Clean up many exception classes.

Errors indicating a user error are now shown with is_user_error on the
exception; use this rather than hardcoding a list of exceptions that should be
handled this way.

Exceptions now inherit from BzrNewException where possible to use consistent
formatting method.

Remove rather obsolete docstring test on Branch.missing_revisions.

Remove dead code from find_merge_base.


Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/requirements.txt
1
 
************
2
 
Requirements
3
 
************
4
 
 
5
 
gcc requirements
6
 
----------------
7
 
 
8
 
* http://lists.gnu.org/archive/html/gnu-arch-users/2004-06/msg00082.html
9
 
* http://gcc.gnu.org/ml/gcc/2004-06/msg00264.html
10
 
 
11
 
Some of these are:
12
 
 
13
 
* Must preserve existing history from CVS; must be able to export back
14
 
  out to CVS in case they change their mind.
15
 
 
16
 
* Support a single central blessed version.
17
 
 
18
 
* Cheap branches and tagging.
19
 
 
20
 
* Handle repeated merges; remember the last time something was merged.
21
 
 
22
 
* Easy cloning.
23
 
 
24
 
* Copy a named patch set (one or more changes) onto a particular
25
 
  branch.
26
 
 
27
 
* Unix, Windows, Mac.
28
 
 
29
 
* What patches changed a particular symbol?
30
 
 
31
 
* annotate function that shows deleted lines.
32
 
 
33
 
* Reliable backups.  (bzr can do this simply by cloning, then
34
 
  mirror-sync.)
35
 
 
36
 
* Scale to enormously wide and long history.
37
 
 
38
 
* Easy to get back to last-known-good state.
39
 
 
40
 
 
41
 
 
42
 
kernel
43
 
------
44
 
 
45
 
 * http://www.kerneltraffic.org/kernel-traffic/kt20030323_210.txt
46
 
 
47
 
   Discussion of BitKeeper, strengths and weaknesses, and
48
 
   interoperation tools.