On Mon, Sep 28, 2009 at 14:30, Rebecca Young <Rebecca.Young_at_amdocs.com> wrote:
>
> Well, that explains it I guess! Since the documentation kind of lumped unix and windows instructions together, I took the following to mean that server administrators could enforce this. Thank you for clearing it up and offering your suggestions!
>
> DOC: “In addition to the per-user configuration area, Subversion also recognizes the existence of a system-wide configuration area. This gives system administrators the ability to establish defaults for all users on a given machine….”
>
What happens in that case is that the first time a user uses
Subversion, the defaults in /etc/subversion will be copied to
~/.subversion
Subsequent changes to those system defaults will *not* be reflected in
the user's configuration.
Not sure if this maps to Windows at all (if so, I don't know where
that default would reside).
> From: Gleason, Todd [mailto:tgleason_at_impac.com]
> Sent: Monday, September 28, 2009 11:20 AM
> To: Bob Archer; Rebecca Young; users_at_subversion.tigris.org
> Subject: RE: Setting auto-props on windows server
>
>
>
> I'm pretty sure auto-props is a client slide configuration directive not server side.
>
>
>
> BOb
>
>
>
>
>
> FWIW, some folks enforce this at commit time with a pre-commit hook. We just have a script that checks and syncs up the client’s config whenever they download a new build, which keeps things mostly in sync.
>
>
>
> --Todd
>
> This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
> you may review at http://www.amdocs.com/email_disclaimer.asp
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2401353
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-28 20:38:27 CEST