merge_msg: improve the "no action is required" message

[next-scripts] / merge_msg

diff --git a/merge_msg b/merge_msg
index e5d80ece7690df283794f4b049c5641ffabaa922..a9695fac89d24bcbdf0ba8c8fed552a40b93e5d0 100755 (executable)
--- a/merge_msg
+++ b/merge_msg
@@ -33,7 +33,12 @@ from the FIXME tree and commit:
 
 from the BRANCH tree.
 
-I fixed it up (see below) and can carry the fix as necessary (no action is required).
+I fixed it up (see below) and can carry the fix as necessary. This
+is now fixed as far as linux-next is concerned, but any non trivial
+conflicts should be mentioned to your upstream maintainer when your tree
+is submitted for merging.  You may also want to consider cooperating
+with the maintainer of the conflicting tree to minimise any particularly
+complex conflicts.
 EOF
 
 exit 0