mike/biboumi
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

grammar: than <-> as

Browse Source
This commit is contained in:
louiz’
2017-01-22 21:32:37 +01:00
parent 5d801ddcd0
commit b660a47367
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/biboumi.1.rst
+1 -1
View File
@@ -297,7 +297,7 @@ On XMPP, unlike on IRC, the displayed order of the messages is the same for
all participants of a MUC. Biboumi can not however provide this feature, as all participants of a MUC. Biboumi can not however provide this feature, as
it cannot know whether the IRC server has received and forwarded the it cannot know whether the IRC server has received and forwarded the
messages to other users. This means that the order of the messages messages to other users. This means that the order of the messages
displayed in your XMPP client may not be the same than the order on other displayed in your XMPP client may not be the same as the order on other
IRC users’. IRC users’.
History History
src/bridge/bridge.cpp
+1 -1
View File
@@ -1029,7 +1029,7 @@ void Bridge::send_xmpp_ping_request(const std::string& nick, const std::string&
const std::string& id) const std::string& id)
{ {
// Use revstr because the forwarded ping to target XMPP user must not be // Use revstr because the forwarded ping to target XMPP user must not be
// the same that the request iq, but we also need to get it back easily // the same as the request iq, but we also need to get it back easily
// (revstr again) // (revstr again)
// Forward to the first resource (arbitrary, based on the “order” of the std::set) only // Forward to the first resource (arbitrary, based on the “order” of the std::set) only
const auto resources = this->resources_in_server[hostname]; const auto resources = this->resources_in_server[hostname];