text: Totally enforce useful rules for important Subversion owned properties.
  Rules on important properties are good for your data store's sanity.
  That's a huge +1 from me. :)
  Bill
  ----
  Do you want a dangerous fugitive staying in your flat?
  No.
  Well, don't upset him and he'll be a nice fugitive staying in your flat.
  > -----Original Message-----
  > From: Karl Fogel [mailto:kfogel@newton.ch.collab.net]
  > Sent: Tuesday, May 21, 2002 10:50 AM
  > To: dev@subversion.tigris.org
  > Subject: proposal for sanity check at propset time
  >
  > We have some properties in the "svn:" namespace that are only
  > meaningful for files, and some that are only meaningful for dirs:
  >
  > svn:mime-type ==> files
  > svn:ignore ==> directories
  > svn:eol-style ==> files
  > svn:keywords ==> files
  > svn:executable ==> files (*)
  > svn:charset ==> files
  > svn:externals ==> directories
  >
  > (* Yes, Unix overloads "executable" to have a meaning for directories,
  > but that's not what we document the executable property to mean, so I
  > don't think Subversion should support that overloading.)
  >
  > Since Subversion manages the "svn:" property namespace anyway, maybe
  > we should protect against setting such properties on the wrong kind of
  > target? Of course, user can pass --force to override:
  >
  > $ svn propset svn:mime-type "text/plain" .
  > Error: "svn:mime-type" is for files, blah blah, use --force to
  override
  > $ svn propset --force svn:mime-type "text/plain" .
  > property `svn:mime-type set on '.'
  > $
  >
  > Thoughts? Objections?
  >
  > -K.