# HG changeset patch
# User Kevin Bullock <kbullock@ringworld.org>
# Date 1359684086 21600
# Node ID 9fbeb61b8ad26eea6ed6983724ac49d7b874892d
# Parent  bf8bbbf4aa4532458d3df6789fbdf5667018fee3
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.

diff -r bf8bbbf4aa45 -r 9fbeb61b8ad2 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