CG: clarify staging branch policy

[lilypond.git] / Documentation / contributor / administration.itexi

diff --git a/Documentation/contributor/administration.itexi b/Documentation/contributor/administration.itexi
index 88c66bea775ba1c741463d11c79d42fb1bf98499..73c317855eb84dc09c65a0b8c96ffa25a79e319b 100644 (file)
--- a/Documentation/contributor/administration.itexi
+++ b/Documentation/contributor/administration.itexi
@@ -254,6 +254,9 @@ these complete error-free. If you have set Patchy up to use email,
 it emails its results to you.  If you haven't, then you can view
 them in a logfile.  It also merges @code{staging} into @code{master}.
 
+@warning{in case the build fails, do not try to push fixes on top of
+staging branch, for details see @ref{Pushing to staging}.}
+
 When you have run Patchy a few successful times with email sending,
 you are ready for running it as a cron job. First, make sure you have
 the following in @file{$HOME/.lilypond-patchy-config} to avoid