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

RFE - Binary props set/unset syntax

From: Karellen <karellen_at_boreworms.com>
Date: 2002-11-08 23:33:06 CET

Greetings all,

After looking at bug 896 scheduled for the next milestone, and reading
the mentioned list thread
http://subversion.tigris.org/servlets/ReadMsg?list=dev&msgNo=21380 I
noticed that the discussion about client syntax for setting/unsetting
binary props (such as svn:executable) trailed off and didn't seem to get
resolved. However, reading the messages gave me an idea on a possible
implementation, and as I haven't been able to find any further
discussion or buggage on it, I thought I'd post.

In the thread, the syntax `svn propset svn:executable on filename', was
mentioned but turning if off (NOT `svn propset svn:executable off
filename') is unintuitive.

Adapting the chmod(1) syntax is mentioned as `svn +x filename', but that
was shot down as `wrong' for subversion, because we use `x' for
something else, and because it has no obvious link to the svn:executable
property on non-unix platforms.

So, how about a marriage of the two?

`svn propset +svn:executable filename'
`svn propset -svn:executable filename'

If property names are not allowed to start with punctuation (Is this
the case? Is there any existing code that this might break?) then it's
not ambiguous, it's relatively intuitive (more so than `+x' and probably
doesn't go against anything already in place. The `+propname' could set
the prop with a null value (but because it exists, it's turned on), and
the `-propname' syntax could be a synonym for `svn propdel propname'
remove the prop, turning it off.

Thoughts?

Karellen.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Nov 8 23:33:29 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.