Hi, Daniel,
Just one workaround idea: uninstall the cygwin svn client, and use one of the "native" windows subversion clients for the command line. They should work fine even when called from Cygwin environment.
Best regards
Markus Schaber
___________________________
We software Automation.
3S-Smart Software Solutions GmbH
Markus Schaber | Developer
Memminger Str. 151 | 87439 Kempten | Germany | Tel. +49-831-54031-0 | Fax +49-831-54031-50
Email: m.schaber@3s-software.com | Web: http://www.3s-software.com
CoDeSys internet forum: http://forum.3s-software.com
Download CoDeSys sample projects: http://www.3s-software.com/index.shtml?sample_projects
Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915
> -----Ursprüngliche Nachricht-----
> Von: Daniel Schepler [mailto:dschepler_at_scalable-networks.com]
> Gesendet: Freitag, 27. Mai 2011 20:11
> An: Bob Archer; users_at_subversion.apache.org
> Cc: Jesse Liesch
> Betreff: RE: Disabling automatic setting of svn:executable property
>
> The problem is that any file created by a non-Cygwin Windows program will
> show up in Cygwin as mode 777 by default, unless you do a chmod from the
> Cygwin shell afterwards. What I'm looking for is a solution that would be
> convenient for the Cygwin/Windows users and not subject to the "user needs
> to do N things before every svn add / whoops, user forgot step M out of N"
> problem.
>
> I spent a bit of effort when we did our recent cvs2svn fixing up
> inconsistent permissions in the old CVS repository. But it looks like
> pretty soon we'll have a similar situation in the Subversion repository
> unless we can find a good way to prevent execute bits from being
> accidentally set. I'd hate to have to set up a draconian pre-commit hook
> that rejects commits setting non-program/script files to executable. And
> I would find it hard to believe we're the first to have this issue.
> --
> Daniel
>
> -----Original Message-----
> From: Bob Archer [mailto:Bob.Archer_at_amsi.com]
> Sent: Friday, May 27, 2011 6:43 AM
> To: Daniel Schepler; users_at_subversion.apache.org
> Cc: Jesse Liesch
> Subject: RE: Disabling automatic setting of svn:executable property
>
> > We have a lot of users using Subversion under Cygwin, which means that
> > any files they add get marked as executable by default (and almost
> > always uselessly). Is there any way to disable the automatic setting
> > of the svn:executable property on an "svn add"?
> > The closest thing I see in the manual is --no-auto-props, but that
> > doesn't seem to have the desired effect in a quick test.
> > --
> > Daniel
>
> Is the execute property of the file on? I expect it is. Use chmod to turn
> it off before adding the file.
>
> (this is mostly an educated guess since I don't use cygwin).
>
> BOb
Received on 2011-05-30 08:06:16 CEST