On 6/26/07, Jan-H. Jagla <jhjagla@gams.com> wrote:
> Ryan, thanks for the reply
>
> >> I'd like to be able to use
> >>
> >> * = svn:eol-style=native
> >>
> >> in the config file since we have about 500 file types in our repository.
> >
> > Hopefully none of your file types are binary, because
> > svn:eol-style=native will be applied to them as well, which will likely
> > corrupt them irreversibly.
>
> AFAIK, svn doesn't apply the svn:eol-tyle property to binary files but
> rather returns an error message, so that's fine.
But what if you come across a new binary type which isn't known to be
binary before attempting to apply that property?
> >> However, I would like to specify some file types which get special
> >> properties, e.g. *.pdf = svn:mime-type=application/pdf
> >>
> >> Is this possible and in which order do I have to arrange the entries
> >> in the config files?
> >
> > Good question. Maybe you can unset the svn:eol-style then too. I don't
> > know if it's possible or what order to do it in. You could experiment
> > and report back to us...
>
> The subversion book says:
>
> "Multiple matches on a file will result in multiple propsets for that
> file; however, there is no guarantee that auto-props will be applied in
> the order in which they are listed in the config file, so you can't have
> one rule "override" another."
>
> that's why I would like to know if anyone has experience with multiple
> matches and whats the best order?
Per the section of the manual you quoted, the order doesn't matter.
There's no guarantee that it'll be followed, so there's really no
point in paying attention to it.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jun 26 14:24:15 2007