diff options
| author | Andrey Lihatskiy <118752495+marchcat@users.noreply.github.com> | 2026-08-13 20:18:46 +0300 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2026-08-13 20:18:46 +0300 |
| commit | 039c1b4b027a5f34449a934d9aea0cea8a2c7659 (patch) | |
| tree | f27a36ca21ab04d7e3ddb0c65ea39ee063252611 /indra/llfilesystem/lldiskcache.cpp | |
| parent | c8730531ee1a030c4e71f2b7ddb7d3394c9af7b7 (diff) | |
| parent | f376c52ee2a22b3b58263d86566394e80626fc1a (diff) | |
Merge pull request #6133 from secondlife/marchcat/lua-linux-develop
geenz/linux-to-develop to lua_editor
Diffstat (limited to 'indra/llfilesystem/lldiskcache.cpp')
| -rw-r--r-- | indra/llfilesystem/lldiskcache.cpp | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/indra/llfilesystem/lldiskcache.cpp b/indra/llfilesystem/lldiskcache.cpp index 9b674d5528..e7b43e15e2 100644 --- a/indra/llfilesystem/lldiskcache.cpp +++ b/indra/llfilesystem/lldiskcache.cpp @@ -64,9 +64,9 @@ LLDiskCache::LLDiskCache(const std::string& cache_dir, // WARNING: purge() is called by LLPurgeDiskCacheThread. As such it must // NOT touch any LLDiskCache data without introducing and locking a mutex! -// Interaction through the filesystem itself should be safe. Let’s say thread +// Interaction through the filesystem itself should be safe. Let's say thread // A is accessing the cache file for reading/writing and thread B is trimming -// the cache. Let’s also assume using llifstream to open a file and +// the cache. Let's also assume using llifstream to open a file and // std::filesystem::remove are not atomic (which will be pretty much the // case). |