On Thu, Nov 1, 2012 at 7:08 AM, Stefan Sperling <stsp_at_elego.de> wrote:
> On Wed, Oct 31, 2012 at 10:56:31PM -0000, pburba_at_apache.org wrote:
>> Author: pburba
>> Date: Wed Oct 31 22:56:30 2012
>> New Revision: 1404404
>> URL: http://svn.apache.org/viewvc?rev=1404404&view=rev
>> * site/publish/docs/release-notes/1.8.html: Complete the entry for
>> repository dictated configuration. A few other minor wording
>> and terminology tweaks.
>> +<p>Two new Subversion reserved properties, <tt>svn:inheritable-auto-props</tt>
>> +and <tt>svn:inheritable-ignore</tt> make use of the new
>> +inherited properties feature to provide additional
>> +configuration information that overrides/extends some of the settings
>> +found in the user's <a href="http://svnbook.red-bean.com/en/1.7/svn-book.html#svn.advanced.confarea.opts.config"
>> +>runtime configuration</a>. The <tt>svn:inheritable-auto-props</tt>
>> +property overrides/extends the <tt>auto-props</tt> configuration setting.
>> +The <tt>svn:inheritable-ignores</tt> property extends the
>> +<tt>global-ignores</tt> configuration setting as well as the
>> +<tt>svn:ignore</tt> property.</p>
> Hey Paul,
> svn:mergeinfo is also inheritable (ignoring subtle differences in
> inheritance semantics), yet we don't call it svn:inheritable-mergeinfo.
> So I'm wondering if we can find better names for these new properties.
> What about svn:default-ignores and svn:default-auto-props?
> Or perhaps names which correspond to the configuration file counterparts,
> svn:global-ignores and svn:auto-props?
In case you missed it this was already discussed a little in this
I'm mostly open to whatever the majority of folks want to call these
properties. I personally favor names that are:
1) Parallel the config names and describe the basic purpose, i.e.
".*auto-props.*" and ".*ignores.*"
2) Are not impossibly long and unwieldy
3) Convey the fact that Subversion considers the property inheritable.
I suspect we are all in agreement in #1 and #2, it's #3 some don't
Re svn:mergeinfo, I think that's a unique case which has several
characteristics that don't necessarily set good precedents for generic
inheritable properties (e.g. can inherit from unreadable parent, only
inherits from nearest parent). If nothing else, since it predates the
inheritable property work, its naming scheme shouldn't hold much
influence over what we do going forward.
Paul T. Burba
CollabNet, Inc. -- www.collab.net -- Enterprise Cloud Development
Received on 2012-11-01 14:41:13 CET