[test] Problems with UTF-8 paths in GIT.
This commit < https://github.com/boostorg/filesystem/commit/785d521b54140763dd23ef091a18d7196006c787> is causing me some problems with some git clients. In particular the git client in Eclipse errors out with some unsupported / invalid messages. I know why those dir names are the way they are.. But we still are supposed to follow the naming rules we agreed to < http://www.boost.org/development/requirements.html#Directory_structure>. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
Rene Rivera
On Mon, Jan 5, 2015 at 12:15 PM, Rene Rivera
This commit <
https://github.com/boostorg/filesystem/commit/785d521b54140763dd23ef091a18d7...
is causing me some problems with some git clients. In particular the git client in Eclipse errors out with some unsupported / invalid messages. I know why those dir names are the way they are.. But we still are supposed to follow the naming rules we agreed to < http://www.boost.org/development/requirements.html#Directory_structure>.
How about if I move those directories and files to a different branch? I really don't want to lose them since we do get bug reports involving Asian characters and it is handy to have test cases available. --Beman
On Mon, Jan 5, 2015 at 11:39 AM, Beman Dawes
On Mon, Jan 5, 2015 at 12:15 PM, Rene Rivera
wrote: This commit <
https://github.com/boostorg/filesystem/commit/785d521b54140763dd23ef091a18d7...
is causing me some problems with some git clients. In particular the git client in Eclipse errors out with some unsupported / invalid messages. I know why those dir names are the way they are.. But we still are supposed to follow the naming rules we agreed to < http://www.boost.org/development/requirements.html#Directory_structure>.
How about if I move those directories and files to a different branch? I really don't want to lose them since we do get bug reports involving Asian characters and it is handy to have test cases available.
That might fix it. Don't really know which part of the git process it failed on. So not sure. Another option is to put that structure in a ZIP or TAR and add the archive to GIT. And yet another is to dynamically create that structure (assuming you can of course) with a script or program. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail
participants (3)
-
Beman Dawes
-
Gennadiy Rozental
-
Rene Rivera