mirror of
https://github.com/facebook/sapling.git
synced 2024-10-09 16:31:02 +03:00
8853701e91
Summary: The world has moved on utf-8 as the default encoding for files and data, but EdenFS still accepts non utf-8 filenames to be written to it. In fact, most of the time when a non utf-8 file is written to the working copy, and even though EdenFS handles it properly, Mercurial ends up freaking out and crash. In all of these cases, non-utf8 files were not intentional, and thus refusing to create them wouldn't be a loss of functionality. Note that this diff makes the asumption that Mercurial's manifest only accept utf8 path, and thus we only have to protect against files being created in the working copy that aren't utf8. The unfortunate part of this diff is that it makes importing trees a bit more expensive as testing that a path is utf8 valid is not free. Reviewed By: chadaustin Differential Revision: D25442975 fbshipit-source-id: 89341a004272736a61639751da43c2e9c673d5b3 |
||
|---|---|---|
| .. | ||
| test | ||
| CachedParsedFileMonitor.h | ||
| CheckoutConfig.cpp | ||
| CheckoutConfig.h | ||
| CMakeLists.txt | ||
| ConfigSetting.h | ||
| eden_config.thrift | ||
| EdenConfig.cpp | ||
| EdenConfig.h | ||
| FieldConverter.cpp | ||
| FieldConverter.h | ||
| FileChangeMonitor.cpp | ||
| FileChangeMonitor.h | ||
| ReloadableConfig.cpp | ||
| ReloadableConfig.h | ||
| TomlConfig.h | ||