Changeset 801 in tailor
- Timestamp:
- 09/11/05 20:19:33 (8 years ago)
- Hash name:
- 20050911181933-97f81-dac4ca13fcc7ffd64eaf18f2d78afc4fdd777ec1
- File:
-
- 1 edited
-
vcpx/monotone.py (modified) (4 diffs)
Legend:
- Unmodified
- Added
- Removed
-
vcpx/monotone.py
r800 r801 32 32 This class implements command piping, i.e. a chain of 33 33 ExternalCommand, each feeding its stdout to the stdin of next 34 command in the chain If a command fails, the chain breaks and34 command in the chain. If a command fails, the chain breaks and 35 35 returns error. 36 36 … … 58 58 """ 59 59 Monotone changesets differ from standard Changeset because: 60 60 61 1. only the "revision" field is used for eq/ne comparison 61 62 2. have additional properties used to handle history linearization … … 302 303 def convertDiff(self, chset): 303 304 """ 304 Fills a chset with the details data coming by a diff be etween305 Fills a chset with the details data coming by a diff between 305 306 chset lin_ancestor and revision (i.e. the linearized history) 306 307 """ … … 396 397 This class is used to create changesets from revision ids. 397 398 398 Since most backends (and tailor itself) do esn't support monotone399 Since most backends (and tailor itself) don't support monotone 399 400 multihead feature, sometimes we need to linearize the revision 400 graph, creating syntethized (i.e. fake) edges be etween revisions.401 graph, creating syntethized (i.e. fake) edges between revisions. 401 402 402 403 The revision itself is real, only its ancestors (and all changes 403 be etween) are faked.404 between) are faked. 404 405 405 406 To properly do this, changeset are created by a mixture of 'log'
Note: See TracChangeset
for help on using the changeset viewer.
