Return-Path: 
 <commits-return-24244-apmail-subversion-commits-archive=subversion.apache.org@subversion.apache.org>
X-Original-To: apmail-subversion-commits-archive@minotaur.apache.org
Delivered-To: apmail-subversion-commits-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 04111D3AB
	for <apmail-subversion-commits-archive@minotaur.apache.org>;
 Wed, 31 Oct 2012 19:31:22 +0000 (UTC)
Received: (qmail 14741 invoked by uid 500); 31 Oct 2012 19:31:21 -0000
Delivered-To: apmail-subversion-commits-archive@subversion.apache.org
Received: (qmail 14712 invoked by uid 500); 31 Oct 2012 19:31:21 -0000
Mailing-List: contact commits-help@subversion.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@subversion.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@subversion.apache.org>
List-Post: <mailto:commits@subversion.apache.org>
List-Id: <commits.subversion.apache.org>
Reply-To: dev@subversion.apache.org
Delivered-To: mailing list commits@subversion.apache.org
Received: (qmail 14705 invoked by uid 99); 31 Oct 2012 19:31:21 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Oct 2012 19:31:21 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.131] (HELO eos.apache.org) (140.211.11.131)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Oct 2012 19:31:20 +0000
Received: from eos.apache.org (localhost [127.0.0.1])
	by eos.apache.org (Postfix) with ESMTP id 357A3883
	for <commits@subversion.apache.org>; Wed, 31 Oct 2012 19:31:00 +0000 (UTC)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache subversion Wiki <commits@subversion.apache.org>
To: Apache subversion Wiki <commits@subversion.apache.org>
Date: Wed, 31 Oct 2012 19:31:00 -0000
Message-ID: <20121031193100.99552.87442@eos.apache.org>
Subject: 
 =?utf-8?q?=5BSubversion_Wiki=5D_Trivial_Update_of_=22Inheritable-Ignores-?=
 =?utf-8?q?AutoProps=22_by_pburba?=
Auto-Submitted: auto-generated
X-Virus-Checked: Checked by ClamAV on apache.org

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Subversion Wiki" fo=
r change notification.

The "Inheritable-Ignores-AutoProps" page has been changed by pburba:
http://wiki.apache.org/subversion/Inheritable-Ignores-AutoProps?action=3Ddi=
ff&rev1=3D8&rev2=3D9

Comment:
Add ToC

  ## page was renamed from InheritableAutoProps
  =3D=3D Repository Dictated Configuration Via Inheritable Properties =3D=
=3D
+ =

+ <<TableOfContents>>
+ =

  Many software development shops of non-trivial size  desire to have (and =
to the extent possible, to enforce) a uniform  configuration environment am=
ong the various clients which commit to  their repositories.  Although thes=
e shops may have some ability to  control the environment on the client mac=
hines (dictating software  versions, etc), expecting humans to consistently=
 set and maintain  various runtime configuration parameters in accordance w=
ith corporate  policy and on every repository-accessing client computer is =
both  error-prone and unscalable.
  =

  Subversion  already provides the means of enforcing much (but not all) of=
 this  configuration through the hook script mechanism, but at best this ca=
n  only punish non-compliant client behavior and clumsily recommend  config=
uration changes (which, again, a human must implement on their  client comp=
uter). An administrator could save a good deal of time and frustration if t=
hey could set a special configuration property on the root <<FootNote(Of co=
urse the property need not be set on the root of repository.  It might be s=
et on the root of some project folder, e.g. ^/subversion in our own repos, =
or some other root.  The point is that the property doesn't need to be set =
on every directory to affect the whole repository (or some large subtree) t=
he way that svn:ignore currently requires)>> of their repository which well=
-behaved clients (treating the special configuration property as inheritabl=
e) would use to override the user's local config file settings.