[
https://issues.apache.org/jira/browse/SVN-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15383854#comment-15383854
]
Markus Kuhn commented on SVN-1974:
----------------------------------
The original feature request 12 years ago for repo-side control of the
[auto-props] configuration of a client was properly fixed in 2013 with the
addition of svn:auto-props in Subversion 1.8. It works wonderfully!
Therefore, I would suggest to close this issue now.
If there is still any additional centralized-configuration functionality
missing that users want, I think it would be much cleaner and neater if the
proponents of that opened a new feature request that presents at the top a
clear use case for what Subversion is still missing today, so that that can be
added to the roadmap instead. Leaving a 12-year old issue open that has
actually been resolved years ago only confuses newcomers, IMHO.
> server-side config which 'broadcasts' to clients
> ------------------------------------------------
>
> Key: SVN-1974
> URL: https://issues.apache.org/jira/browse/SVN-1974
> Project: Subversion
> Issue Type: New Feature
> Components: unknown
> Affects Versions: all
> Reporter: Subversion Importer
> Labels: tortoisesvn
> Fix For: 2.0-consider
>
>
> {noformat:nopanel=true}
> I've tried finding this issue, and issues 1002, 1233 and 1813 come close-ish,
> but they are not what I am looking for.
> I am using a SVN repository with Apache httpd for a java project. The project
> directory has all kinds of files in it: java source, pdf files, word docs,
> excel
> files, etc. I would like these files to have the correct svn:mime-type
> property
> when I (or my coworkers) add a file. Setting the mime type is great in
> combination with Apache and browser access. The usual way to do this is
> through
> the auto-props feature on the _client side_. This has turned out to be a pain
> to
> work with.
> First, I (as SVN repository admin) have no way to enforce "good use" with a
> "cvswrappers" type of file. We needed to make a separate .reg file for the
> autoprops settings, keep that under version control, and make sure that
> everybody merged this when they started working on the project, on a new
> machine, or when Windows had been reinstalled (oh yes that happens sometimes
> :)., etc.
> Second, the client config settings are not per repository. I have a case where
> in one repository the HTML files are docs and should be text/html, and another
> repository where they are source and they should be text/plain... no can do
> with
> a global client config...
> {noformat}
> Original issue reported by *beaumose*
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
