changeset 5485:457d8003e840

unstable-list: add information about when/why orphan appears (maybe a bit short?), but making the distinction between the local and remote case seems useful.
author Pierre-Yves David <pierre-yves.david@octobus.net>
date Fri, 14 Aug 2020 18:09:42 +0200
parents e3302ad5ad77
children 381df06460e8
files docs/troubles-handling.rst
diffstat 1 files changed, 7 insertions(+), 0 deletions(-) [+]
line wrap: on
line diff
--- a/docs/troubles-handling.rst	Fri Aug 14 18:08:48 2020 +0200
+++ b/docs/troubles-handling.rst	Fri Aug 14 18:09:42 2020 +0200
@@ -33,6 +33,13 @@
 Cause of trouble
 ****************
 
+Orphan can appears because the use locally rewrite changeset with descendants.
+In this case the orphan are created when the command run.
+
+Orphan can also happens when the users created new changeset on draft that got
+rewritten in another repository. The orphan are then "discovered" when the
+obsolescence information of the ancestors is pulled in the local repository.
+
 Source of Complexity
 ********************