diff options
| author | santoslgl01-web <santoslgl01@gmail.com> | 2026-04-29 15:27:15 -0300 |
|---|---|---|
| committer | Andrey Kleshchev <117672381+akleshchev@users.noreply.github.com> | 2026-05-12 01:48:19 +0300 |
| commit | 127fe9bc88ad19d8cbf69be9e09bf9fa2e7abd7b (patch) | |
| tree | 69fdb9ff8d0c517eb87f5fa7ee2cc8adeb97725f /indra/llfilesystem/lldiskcache.cpp | |
| parent | a4e8f716a2cd682e1fd89eafbee45845648cdf72 (diff) | |
fix: replace non-ASCII source comments
Resolves #5664
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 dd7d1a043f..ea33178a1e 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 // boost::filesystem::remove are not atomic (which will be pretty much the // case). |