On windows, it will silently remove trailing whitespace from filenames under certain conditions. We have a test that our Bundle code is able to send a filename that ends in a whitespace and it will be correctly seen when merging that patch. And it was failing on Windows for some reason.... Took a bit to track that down.
IIRC, it was doing it for both NTFS and FAT32.
So I see a couple possibilities:
a) Strip whitespace from the ignore patterns when reading from .bzrignore (if we are going to do trailing whitespace, I would do leading whitespace, too)
b) Strip whitespace from the command line arguments to "bzr ignore". That doesn't help people who use "echo" though.
On windows, it will silently remove trailing whitespace from filenames under certain conditions. We have a test that our Bundle code is able to send a filename that ends in a whitespace and it will be correctly seen when merging that patch. And it was failing on Windows for some reason.... Took a bit to track that down.
IIRC, it was doing it for both NTFS and FAT32.
So I see a couple possibilities:
a) Strip whitespace from the ignore patterns when reading from .bzrignore (if we are going to do trailing whitespace, I would do leading whitespace, too)
b) Strip whitespace from the command line arguments to "bzr ignore". That doesn't help people who use "echo" though.
I'd probably like to do both...