Commits

Martin Geisler  committed ad14c7d

Reflow commit msg text

  • Participants
  • Parent commits 8598727

Comments (0)

Files changed (1)

File implementation

 # User Henrik Stuart <hg@hstuart.dk>
 # Date 1295774638 -3600
 # Node ID af7e034f9ea327eddd524ca69023fe1ec84a433b
-# Parent  0d1dca7d2a041cb1cb6c6bd90608aa87068bde02
+# Parent 0d1dca7d2a041cb1cb6c6bd90608aa87068bde02
 add support for marking changesets as dead
 
-Marking a changeset as dead is, if it is a head, a way to delete a branch of
-development in a safe, append-only manner. A dead changeset "kills" all its
-ancestors that are not reachable from a non-dead head and make them subject to
-revised propagation rules that are outlined below:
+Marking a changeset as dead is, if it is a head, a way to delete a
+branch of development in a safe, append-only manner. A dead changeset
+"kills" all its ancestors that are not reachable from a non-dead head
+and make them subject to revised propagation rules that are outlined
+below:
 
   A dead head is propagated if and only if it kills a head.
 
 
   0
 
-After a pull/push, the other repository would just get changeset 3. Had the
-other repository been:
+After a pull/push, the other repository would just get changeset 3.
+Had the other repository been:
 
   0 ---- 1
 
-It would receive both changesets 2 and 3 after a pull/push since 2 kills the
-local non-dead head 1.
+It would receive both changesets 2 and 3 after a pull/push since 2
+kills the local non-dead head 1.
 
 Had the base repository been:
 
    \      \
     ------ 3 ---- 4
 
-Then no matter if the other repository was 0, or 0 ---- 1, then it would
-receive changesets 3 and 4 as new heads, but not changeset 2 as 4 ressurrects
-changeset 1.
+Then no matter if the other repository was 0, or 0 ---- 1, then it
+would receive changesets 3 and 4 as new heads, but not changeset 2 as
+4 ressurrects changeset 1.
 
-hg log and the graphlog extension are extended with knowledge of dead heads, so
-if no revision set is specified, changesets that are dead will not be
-displayed, otherwise it is up to the revision set to indicate whether dead
-changesets should or should not be displayed using the new "dead(optionalset)"
-revision set function.
+hg log and the graphlog extension are extended with knowledge of dead
+heads, so if no revision set is specified, changesets that are dead
+will not be displayed, otherwise it is up to the revision set to
+indicate whether dead changesets should or should not be displayed
+using the new "dead(optionalset)" revision set function.
 
 Co-authors: Erik Zielke and Martin Geisler