Mercurial Mercurial > pub > hg > evolve / diff
summary | shortlog | changelog | graph | tags | bookmarks | branches | files | changeset | file | latest | revisions | annotate | diff | comparison | raw | help
Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
docs/sharing.rst
changeset 4620 a05bfdf372fb
parent 4619 93514c421528
child 4621 8784dfc6537c 
--- a/docs/sharing.rst	Sat Apr 27 21:27:54 2019 -0400
+++ b/docs/sharing.rst	Sat Apr 27 21:41:04 2019 -0400
@@ -512,7 +512,7 @@
 the most common type of unstable changeset. (Recall that a
 non-obsolete changeset with obsolete ancestors is an orphan.)
 
-Two other types of instability can happen: *divergent* and
+Two other types of instability can happen: *content-divergent* and
 *bumped* changesets. Both are more likely with shared mutable
 history, especially mutable history shared by multiple developers.
 
@@ -556,11 +556,11 @@
 
 and add the same text.
 
-Example 6: Divergent changesets
-===============================
+Example 6: Content-divergent changesets
+=======================================
 
 When an obsolete changeset has two successors, those successors are
-*divergent*. One way to get into such a situation is by failing
+*content-divergent*. One way to get into such a situation is by failing
 to communicate with your teammates. Let's see how that might happen.
 
 First, we'll have Bob commit a bug fix that could still be improved::
@@ -596,11 +596,11 @@
   [...]
   added 1 changesets with 1 changes to 2 files (+1 heads)
   (run 'hg heads' to see heads, 'hg merge' to merge)
-  2 new divergent changesets
+  2 new content-divergent changesets
 
 Figure 9 shows the situation in Bob's repository.
 
-  [figure SG09: Bob's repo with 2 heads for the 2 divergent changesets, 6:a360 and 7:e3f9; wc is at 6:a360; both are successors of obsolete 4:2fe6, hence divergence]
+  [figure SG09: Bob's repo with 2 heads for the 2 content-divergent changesets, 6:a360 and 7:e3f9; wc is at 6:a360; both are successors of obsolete 4:2fe6, hence divergence]
 
 Now we need to get out of trouble. As usual, the answer is to evolve
 history. ::
@@ -619,7 +619,7 @@
 (``internal:other``) that will take Alice's changes over Bob's. (You
 might wonder why Bob wouldn't prefer his own changes by using
 ``internal:local``. He's avoiding a `bug`_ in ``evolve`` that occurs
-when evolving divergent changesets using ``internal:local``.)
+when evolving content-divergent changesets using ``internal:local``.)
 
 # XXX this link does not work
 .. _`bug`: https://bitbucket.org/marmoute/mutable-history/issue/48/
evolve