[win32] Probably bug: tracking permissions bits on windows

[Alexander Belchenko]

Aaron Bentley wrote:
> Martin Pool wrote:
> | Yes; on Windows I think we would want to store the permissions in the
> | working inventory and pay no attention to the permissions of the working
> | copy files.
> 
> Because of this issue, and symlinks, I think we should have a
> "WindowsWorkingTree", so we can separate that behavior out.
> 
> I don't know exactly what to do with symlinks.  It may make sense to
> create a plaintext file on disk with the symlink target as its text. The
> WindowsWorkingTree would cause it to appear to bzrlib as a symlink.
> That would allow Windows users to manipulate the symlink target
> directly, and provide a dummy file, making it harder to accidentally
> reuse that filename.

Creating real text file instead of symlink may be interesting idea. 
AFAIK no one SCM does not provide this feature, but may be I'm wrong. 
But probably needs for this feature will be very rare.

> Windows was the reason I wanted to represent the executable bit, because
> I imagined a "bzr set-property" command that Windows users would be able
> to use to set/unset the executable bit.

It's good idea. I'm two hands up for this feature. It will be useful for 
making projects with native linux support of executable bit in setup 
scripts per example.

Alexander