Hmmm. Eeeuuww :-). Thanks for pointing this out. Can you stick this
in the issue, so it's noticed when someone starts thinking about
coding?
Solution: maybe don't notice x-bit by default, but offer a flag (long
opt only) to notice & use it? People will often forget the flag even
when they want it, which is too bad, but at least it's there for those
who remember...
-K
Peter Davis <peter@pdavis.cx> writes:
> On Tuesday 13 August 2002 12:08, issues@subversion.tigris.org wrote:
> > + When importing, we should detect executableness on files and set the
> > + svn:executable property automatically.
>
> One problem: if I mount an smb share in Linux, (almost) all files are
> executable, whether they should be or not. This is because Windows doesn't
> have an executable bit, and Samba uses those bits to store Windows' archive,
> read-only and system attributes.
>
> So this might not be totally reliable, and I'd rather have to go through and
> manually set svn:executable on my few executable files than have to unset it
> on all my other files. This could affect lots of people who use svn at work;
> at my work in the past, all my files were on an NT fileserver mounted through
> Samba, even my working directories. Annoying, but real.
>
> Also, it'd be nice to avoid asymmetry with svn on Windows, where I don't know
> how this could work (other than just executable for *.{exe,bat,com}).
>
>
> I really like your idea for issue-869 though.
>
> --
> Peter Davis
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 16 08:29:13 2002