diff options
| author | Jonathan "Geenz" Goodman <geenz@geenzo.com> | 2026-08-14 19:08:11 -0400 |
|---|---|---|
| committer | Jonathan "Geenz" Goodman <geenz@geenzo.com> | 2026-08-14 19:08:11 -0400 |
| commit | 66ff4c75bc2d594a41dfe22d85139311567b8e97 (patch) | |
| tree | 08eec3889838cebf272e10ee34153a91667d4781 /indra/llfilesystem/lldiskcache.cpp | |
| parent | 0a32098d4a603bc2a25fc68bbeaa1e980f0c1fe1 (diff) | |
| parent | 305bebbdb3b16b10b6011b5b3b5d63ee7c7334be (diff) | |
Merge branch 'project/lua_editor' into pepper/pchat-revamp
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). |