On Sun, 2009-04-19 at 17:03 +0000, Stefan Müller wrote:
> Ok I had a look at the log file and it states that the repository was created with the default os encoding - which is cp1252 in my case (when running Windows). In Linux it is UTF-8 so I guess this is the fault. If this is correct this bug is invalid?
> Sorry...
I would certainly expect issues sharing a working tree with two
different filename encodings - those issues should turn up outside just
bzr itself though ;).
You could try overriding your fs encoding on linux to be the same as it
is on windows, so that your file paths match.
On Sun, 2009-04-19 at 17:03 +0000, Stefan Müller wrote:
> Ok I had a look at the log file and it states that the repository was created with the default os encoding - which is cp1252 in my case (when running Windows). In Linux it is UTF-8 so I guess this is the fault. If this is correct this bug is invalid?
> Sorry...
I would certainly expect issues sharing a working tree with two
different filename encodings - those issues should turn up outside just
bzr itself though ;).
You could try overriding your fs encoding on linux to be the same as it
is on windows, so that your file paths match.
-Rob