I'm not the only person who thinks this stinks: http://www.zope.org/DevHome/Subversion/ SubversionConfigurationForLineEndings
On 2006-06-13, at 15:40 EDT, Jim Grandy wrote: > Let's gin up our own and check it into tools/trunk/svn. > > jim > > ps. Here's what your ~/.subversion/config says: > > ### Section for configuring automatic properties. > [auto-props] > ### The format of the entries is: > ### file-name-pattern = propname[=value][;propname[=value]...] > ### The file-name-pattern can contain wildcards (such as '*' and > ### '?'). All entries which match will be applied to the file. > ### Note that auto-props functionality must be enabled, which > ### is typically done by setting the 'enable-auto-props' option. > # *.c = svn:eol-style=native > # *.cpp = svn:eol-style=native > # *.h = svn:eol-style=native > # *.dsp = svn:eol-style=CRLF > # *.dsw = svn:eol-style=CRLF > # *.sh = svn:eol-style=native;svn:executable > # *.txt = svn:eol-style=native > # *.png = svn:mime-type=image/png > # *.jpg = svn:mime-type=image/jpeg > # Makefile = svn:eol-style=native > > On Jun 13, 2006, at 12:32 PM, P T Withington wrote: > >> Is there a nice comprehensive default mapping file we can glom >> onto, or do we need to gin up our own? >> >> On 2006-06-13, at 15:09 EDT, Jim Grandy wrote: >> >>> If you turn on auto-props in your local config, svn can be >>> directed to use more accurate mime types. >>> >>> From the svn book: >>> >>>> Whenever you introduce a file to version control using the svn >>>> add or svn import commands, Subversion runs a >>>> very basic heuristic to determine if that file consists of human- >>>> readable or non-human-readable content. If the latter >>>> is the decision made, Subversion will automatically set the >>>> svn:mime-type property on that file to applica- >>>> tion/octet-stream (the generic “this is a collection of bytes” >>>> MIME type). Of course, if Subversion guesses >>>> incorrectly, or if you wish to set the svn:mime-type property to >>>> something more precise—perhaps image/png >>>> or application/x-shockwave-flash—you can always remove or edit >>>> that property. >>>> >>>> Subversion also provides the auto-props feature, which allows >>>> you to create mappings of filename patterns to prop- >>>> erty names and values. These mappings are made in your runtime >>>> configuration area. They again affect adds and im- >>>> ports, and not only can override any default MIME type decision >>>> made by Subversion during those operations, they >>>> can also set additional Subversion or custom properties, too. >>>> For example, you might create a mapping that says that >>>> any time you add JPEG files—ones that match the pattern *.jpg— >>>> Subversion should automatically set the >>>> svn:mime-type property on those files to image/jpeg. Or perhaps >>>> any files that match *.cpp should have >>>> svn:eol-style set to native, and svn:keywords set to Id. Auto- >>>> prop support is perhaps the handiest >>>> property related tool in the Subversion toolbox. See the section >>>> called “Config” for more about configuring that sup- >>>> port. >>> >>> On Jun 13, 2006, at 11:56 AM, Philip Romanik wrote: >>> >>>> Hi Tucker, >>>> >>>> Do I need to specify the file type as image/gif? When I added >>>> this file I >>>> did not specify any arguments to svn. How do I specify or change >>>> the MIME >>>> type of a file in subversion? >>>> >>>> Thanks! >>>> >>>> Phil >>>> >>>> >>>>> On 2006-06-13, at 10:50 EDT, [EMAIL PROTECTED] wrote: >>>>> >>>>>> Property changes on: openlaszlo/branches/legals/test/lztest/ >>>>>> 1x1.gif >>>>>> _________________________________________________________________ >>>>>> __ >>>>>> Name: svn:mime-type >>>>>> + application/octet-stream >>>>> >>>>> Not image/gif ? >>>> >>>> _______________________________________________ >>>> Laszlo-dev mailing list >>>> [email protected] >>>> http://www.openlaszlo.org/mailman/listinfo/laszlo-dev >>> >> > _______________________________________________ Laszlo-dev mailing list [email protected] http://www.openlaszlo.org/mailman/listinfo/laszlo-dev
