rebase: mention phases in the help stable
authorKevin Bullock <kbullock@ringworld.org>
Thu, 31 Jan 2013 20:01:26 -0600
branchstable
changeset 18516 9fbeb61b8ad2
parent 18515 bf8bbbf4aa45
child 18517 0c51532ec233
rebase: mention phases in the help Mention that Mercurial helps you not do what you've just been warned not to do, with a reference to the 'phases' help topic (not the 'phase' command help). Thanks to Pierre-Yves David <pierre-yves.david@ens-lyon.org> for motivating this change and Wagner Bruna <wagner.bruna+mercurial@gmail.com> for advising on how to do it in an i18n-friendly way.
hgext/rebase.py
--- a/hgext/rebase.py	Thu Jan 31 22:36:22 2013 +0100
+++ b/hgext/rebase.py	Thu Jan 31 20:01:26 2013 -0600
@@ -68,6 +68,9 @@
     same rebase or they will end up with duplicated changesets after
     pulling in your rebased changesets.
 
+    In its default configuration, Mercurial will prevent you from
+    rebasing published changes. See :hg:`help phases` for details.
+
     If you don't specify a destination changeset (``-d/--dest``),
     rebase uses the tipmost head of the current named branch as the
     destination. (The destination changeset is not modified by