tests/test-evolve.t
changeset 1414 4198e2fad6ba
parent 1410 2c451fece7a6
child 1422 c868a69c29c5
equal deleted inserted replaced
1413:cf043c659ae3 1414:4198e2fad6ba
    38   > }
    38   > }
    39 
    39 
    40   $ mkcommits() {
    40   $ mkcommits() {
    41   >   for i in $@; do mkcommit $i ; done
    41   >   for i in $@; do mkcommit $i ; done
    42   > }
    42   > }
       
    43 
       
    44 Test the evolution test topic is installed
       
    45 
       
    46   $ hg help evolution
       
    47   Safely Rewriting History
       
    48   """"""""""""""""""""""""
       
    49   
       
    50       Obsolescence markers make it possible to mark changesets that have been
       
    51       deleted or superset in a new version of the changeset.
       
    52   
       
    53       Unlike the previous way of handling such changes, by stripping the old
       
    54       changesets from the repository, obsolescence markers can be propagated
       
    55       between repositories. This allows for a safe and simple way of exchanging
       
    56       mutable history and altering it after the fact. Changeset phases are
       
    57       respected, such that only draft and secret changesets can be altered (see
       
    58       "hg hg phases" for details).
       
    59   
       
    60       Obsolescence is tracked using "obsolete markers", a piece of metadata
       
    61       tracking which changesets have been made obsolete, potential successors
       
    62       for a given changeset, the moment the changeset was marked as obsolete,
       
    63       and the user who performed the rewriting operation. The markers are stored
       
    64       separately from standard changeset data can be exchanged without any of
       
    65       the precursor changesets, preventing unnecessary exchange of obsolescence
       
    66       data.
       
    67   
       
    68       The complete set of obsolescence markers describes a history of changeset
       
    69       modifications that is orthogonal to the repository history of file
       
    70       modifications. This changeset history allows for detection and automatic
       
    71       resolution of edge cases arising from multiple users rewriting the same
       
    72       part of history concurrently.
       
    73   
       
    74       Current feature status
       
    75       ======================
       
    76   
       
    77       This feature is still in development.  If you see this help, you have
       
    78       enable an extension that turned this feature on.
       
    79   
       
    80       Obsolescence markers will be exchanged between repositories that
       
    81       explicitly assert support for the obsolescence feature (this can currently
       
    82       only be done via an extension).
    43 
    83 
    44 various init
    84 various init
    45 
    85 
    46   $ hg init local
    86   $ hg init local
    47   $ cd local
    87   $ cd local