Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kazuhiko Shiozaki
gitlab-ce
Commits
4a389e76
Commit
4a389e76
authored
Dec 16, 2014
by
Jacob Vosmaer
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Another comment fix
parent
49f4fe8c
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
config/initializers/redis-store-fix-expiry.rb
config/initializers/redis-store-fix-expiry.rb
+2
-2
No files found.
config/initializers/redis-store-fix-expiry.rb
View file @
4a389e76
...
@@ -21,8 +21,8 @@ module Gitlab
...
@@ -21,8 +21,8 @@ module Gitlab
# Our new definitions of #setex and #expire above assume that the
# Our new definitions of #setex and #expire above assume that the
# #namespace method exists. Because we cannot be sure of that, we
# #namespace method exists. Because we cannot be sure of that, we
# re-implement the #namespace method from Redis::Store::Namespace so
# re-implement the #namespace method from Redis::Store::Namespace so
# that it
all Redis::Store instances, whether they use namespacing or
# that it
is available for all Redis::Store instances, whether they use
# not.
# n
amespacing or n
ot.
#
#
# Based on lib/redis/store/namespace.rb L49-51 (redis-store 1.1.4)
# Based on lib/redis/store/namespace.rb L49-51 (redis-store 1.1.4)
def
namespace
(
key
)
def
namespace
(
key
)
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment