Rev 5964: (spiv) Clarify wording of fetch.txt regarding stacking invariants and in file:///home/pqm/archives/thelove/bzr/%2Btrunk/

[Canonical.com Patch Queue Manager]

At file:///home/pqm/archives/thelove/bzr/%2Btrunk/

------------------------------------------------------------
revno: 5964 [merge]
revision-id: pqm at pqm.ubuntu.com-20110609082500-vn5pctkfv1utnp0x
parent: pqm at pqm.ubuntu.com-20110608135130-lmzibvvzxrxwci0t
parent: andrew.bennetts at canonical.com-20110609073832-dt6oww033iexli4l
committer: Canonical.com Patch Queue Manager <pqm at pqm.ubuntu.com>
branch nick: +trunk
timestamp: Thu 2011-06-09 08:25:00 +0000
message:
  (spiv) Clarify wording of fetch.txt regarding stacking invariants and
   revisions with multiple parents. (Andrew Bennetts)
modified:
  doc/developers/fetch.txt       fetch.txt-20110106062538-wc8zxl1vzf1btj3h-1
=== modified file 'doc/developers/fetch.txt'
--- a/doc/developers/fetch.txt	2011-06-07 07:53:47 +0000
+++ b/doc/developers/fetch.txt	2011-06-09 07:38:32 +0000
@@ -125,7 +125,7 @@
 complete streams of that data.
 
 What about revisions at the stacking boundary with more than one parent?
-All of their parent revisions must be present, as a client may ask for a
+All of the parent inventories must be present, as a client may ask for a
 stream up to any parent, not just the left-hand parent.  If any parent is
 absent then all texts must be present instead.  Otherwise there will be
 the strange situation where some fetches of a revision will succeed and