Update comment that says we dont send simplemodes in FJOIN, we do now.

git-svn-id: http://svn.inspircd.org/repository/trunk/inspircd@10635 e03df62e-2008-0410-955e-edbf42e46eb7

diff --git a/src/modules/m_spanningtree/fjoin.cpp b/src/modules/m_spanningtree/fjoin.cpp
index fa61cea4a055ea078615ca0889319a717c2ac436..ee6c6c02a16443304c38b08874daadb6f13d5dbe 100644 (file)
--- a/src/modules/m_spanningtree/fjoin.cpp
+++ b/src/modules/m_spanningtree/fjoin.cpp
@@ -49,13 +49,6 @@ bool TreeSocket::ForceJoin(const std::string &source, std::deque<std::string> &p
         * The winning side on the other hand will ignore all user modes from the
         * losing side, so only its own modes get applied. Life is simple for those
         * who succeed at internets. :-)
-        *
-        * NOTE: Unlike TS6 and dreamforge and other protocols which have SJOIN,
-        * FJOIN does not contain the simple-modes such as +iklmnsp. Why not,
-        * you ask? Well, quite simply because we don't need to. They'll be sent
-        * after the FJOIN by FMODE, and FMODE is timestamped, so in the event
-        * the losing side sends any modes for the channel which shouldnt win,
-        * they wont as their timestamp will be too high :-)
         */
        if (params.size() < 3)
                return true;