Rev 2492: Review feedback. in file:///home/robertc/source/baz/roadmap/

Robert Collins robertc at robertcollins.net
Mon Jun 4 04:39:52 BST 2007


At file:///home/robertc/source/baz/roadmap/

------------------------------------------------------------
revno: 2492
revision-id: robertc at robertcollins.net-20070604033948-erld0bugxcbo62gf
parent: robertc at robertcollins.net-20070604005154-yvx2q8jnwiprw6du
committer: Robert Collins <robertc at robertcollins.net>
branch nick: roadmap
timestamp: Mon 2007-06-04 13:39:48 +1000
message:
  Review feedback.
modified:
  doc/developers/add.txt         add.txt-20070515094933-xhgz3xjc7o0edok0-2
  doc/developers/incremental-push-pull.txt incrementalpushpull.-20070508045640-zneiu1yzbci574c6-1
  doc/developers/revert.txt      revert.txt-20070515111013-grc9hgp21zxqbwbl-1
=== modified file 'doc/developers/add.txt'
--- a/doc/developers/add.txt	2007-05-15 09:49:46 +0000
+++ b/doc/developers/add.txt	2007-06-04 03:39:48 +0000
@@ -27,8 +27,8 @@
 Per file algorithm
 ==================
 
-1. If the path is versioned, and it is a directory, push onto the recurse stack.
-1. If the path is supplied by the user or is not ignored, version it, and if a
+#. If the path is versioned, and it is a directory, push onto the recurse stack.
+#. If the path is supplied by the user or is not ignored, version it, and if a 
    directory, push onto the recurse stack. Versioning the path may require
    versioning the paths parents.
-1. Output or otherwise record the ignored rule as per the user interface selected.
+#. Output or otherwise record the ignored rule as per the user interface selected.

=== modified file 'doc/developers/incremental-push-pull.txt'
--- a/doc/developers/incremental-push-pull.txt	2007-05-18 18:12:12 +0000
+++ b/doc/developers/incremental-push-pull.txt	2007-06-04 03:39:48 +0000
@@ -246,9 +246,13 @@
 copy ebough data to recreate snapshots
 avoid ending up wth corrupt/bad data
 
-setup
-look at graph of revisions for ~N comits to deretmine eligibility for 
-  if preserve mainline is on, check LH only
+Notes from London
+=================
+
+ #. setup
+
+   look at graph of revisions for ~N comits to deretmine eligibility for 
+   if preserve mainline is on, check LH only
 
     identify objects to send that are not on the client repo
       - revision - may be proportional to the graph
@@ -256,17 +260,20 @@
       - texts     - proportional to work
       - signatures - ???
 
-data transmission
-- send data proportional to the new information
-- validate the data [ validate the sha1 of the full text of each transmitted text.
-                      validate the sha1:name mapping in each newly referenced ivnentory item.
-		      validate the sha1 of the XML of each inventory against the revision. *** this is proportional to tree size and must be fixed
-		      ]
-
-- write the data to the local repo.
-
-should output the file texts needed by the merge as by product of the transmission
-
-tree application
-combine the output from the transmission step with additional 'new work data' for anything already in the local repository that is new in this tree.
+ #. data transmission
+
+  * send data proportional to the new information
+  * validate the data:
+
+   #. validate the sha1 of the full text of each transmitted text.
+   #. validate the sha1:name mapping in each newly referenced inventory item.
+   #. validate the sha1 of the XML of each inventory against the revision.
+      *** this is proportional to tree size and must be fixed ***
+
+ #. write the data to the local repo.
+    The API should output the file texts needed by the merge as by product of the transmission
+
+ #. tree application
+
+Combine the output from the transmission step with additional 'new work data' for anything already in the local repository that is new in this tree.
 should write new files and stat existing files proportional to the count of the new work and the size of the full texts.

=== modified file 'doc/developers/revert.txt'
--- a/doc/developers/revert.txt	2007-05-15 11:26:23 +0000
+++ b/doc/developers/revert.txt	2007-06-04 03:39:48 +0000
@@ -17,7 +17,7 @@
 for the selected scopes, for each element in the wt:
 
  1. get hash tree data for that scope.
- 1. get 'new enough' hash data for the siblins of the scope: it can be out of date as long as its not older than the last move or rename out of that siblings scope.
+ 1. get 'new enough' hash data for the siblings of the scope: it can be out of date as long as its not older than the last move or rename out of that siblings scope.
  1. Use the hash tree data to tune the work done in finding matching paths/ids which are different in the two trees.
 
 For each thing that needs to change - group by target directory?



More information about the bazaar-commits mailing list