Commit 88660de2 authored by sergeyu@chromium.org's avatar sergeyu@chromium.org

Fix invalid header guards in jingle_session(_manager)?.h

Review URL: https://chromiumcodereview.appspot.com/10825017

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@148410 0039d316-1c4b-4281-b951-d872f2087c98
parent b76470e2
...@@ -2,8 +2,8 @@ ...@@ -2,8 +2,8 @@
// Use of this source code is governed by a BSD-style license that can be // Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file. // found in the LICENSE file.
#ifndef REMOTING_PROTOCOL_PEPPER_SESSION_H_ #ifndef REMOTING_PROTOCOL_JINGLE_SESSION_H_
#define REMOTING_PROTOCOL_PEPPER_SESSION_H_ #define REMOTING_PROTOCOL_JINGLE_SESSION_H_
#include <list> #include <list>
#include <map> #include <map>
...@@ -152,4 +152,4 @@ class JingleSession : public Session, ...@@ -152,4 +152,4 @@ class JingleSession : public Session,
} // namespace protocol } // namespace protocol
} // namespace remoting } // namespace remoting
#endif // REMOTING_PROTOCOL_PEPPER_SESSION_H_ #endif // REMOTING_PROTOCOL_JINGLE_SESSION_H_
...@@ -2,8 +2,8 @@ ...@@ -2,8 +2,8 @@
// Use of this source code is governed by a BSD-style license that can be // Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file. // found in the LICENSE file.
#ifndef REMOTING_PROTOCOL_PEPPER_SESSION_MANAGER_H_ #ifndef REMOTING_PROTOCOL_JINGLE_SESSION_MANAGER_H_
#define REMOTING_PROTOCOL_PEPPER_SESSION_MANAGER_H_ #define REMOTING_PROTOCOL_JINGLE_SESSION_MANAGER_H_
#include <map> #include <map>
#include <list> #include <list>
...@@ -109,4 +109,4 @@ class JingleSessionManager : public SessionManager, ...@@ -109,4 +109,4 @@ class JingleSessionManager : public SessionManager,
} // namespace protocol } // namespace protocol
} // namespace remoting } // namespace remoting
#endif // REMOTING_PROTOCOL_PEPPER_SESSION_MANAGER_H_ #endif // REMOTING_PROTOCOL_JINGLE_SESSION_MANAGER_H_
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment