[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: rev 1784 - trunk trunk/subversion/include trunk/subversion/libsvn_wc trunk/subversion/libsvn_subr

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-04-26 17:50:39 CEST

Karl Fogel <kfogel@newton.ch.collab.net> writes:

> Anyway. Then I saw the way you actually implemented it, and thought
> to myself, "Hmmm, how interesting, Ben came up with a completely
> different way!" And I can't see anything wrong with it. I'm just not
> sure when one would want to force a file not-executable. I can see
> wanting to enforce executablenss, and wanting to ignore
> executableness, but not wanting to enforce *non*-executableness. :-)

You know, Karl, you've persuaded me. Your plan is much simpler, I
like it.

If the svn:executable property merely *exists* then chmod +x will be
run at commit or update time. The exact value is irrelevant.
If the user removes the property in a commit, or receives a removal of
the property, then chmod -x is run.

I think I'll switch to that model now.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 26 17:53:43 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.