From owner-freebsd-doc@FreeBSD.ORG Fri Oct 19 12:36:03 2012 Return-Path: Delivered-To: doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B4EBE62E; Fri, 19 Oct 2012 12:36:03 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from mxout3.bln1.prohost.de (mxout3.bln1.prohost.de [213.160.84.49]) by mx1.freebsd.org (Postfix) with ESMTP id 3DB878FC14; Fri, 19 Oct 2012 12:36:02 +0000 (UTC) Received: from Benedicts-Macbook-Pro.local ([194.29.130.243]) (authenticated bits=0) by mx1.bln1.prohost.de (8.14.1/8.14.1) with ESMTP id q9JCZxuK031777 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 19 Oct 2012 14:36:00 +0200 Message-ID: <50814931.8060207@FreeBSD.org> Date: Fri, 19 Oct 2012 14:36:01 +0200 From: Benedict Reuschling Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 Subject: Re: RFC: standardizing SVN properties in the doc repo References: <50814827.8030707@FreeBSD.org> In-Reply-To: <50814827.8030707@FreeBSD.org> X-Enigmail-Version: 1.4.5 OpenPGP: id=4A819348 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Null-Tag: 1149c64cb14e9a1151c22fa344af7ec8 Cc: FBSD Doc project , www@FreeBSD.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: bcr@FreeBSD.org List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Oct 2012 12:36:03 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 19.10.12 14:31, schrieb Gabor Kovesdan: > Hi, > > currently, the proper use of SVN properties and dealing with file types > are not standardized in the doc repo. I propose the following policy for > the repo: > > - Use the .sh extension for shell scripts so that they can be easily > identified as such > > - Always add the $FreeBSD$ keyword and set svn:keywords to FreeBSD=%H if > you create a text non-binary file that support escaping it. > > - Only set fbsd:nokeywords for non-binary (i.e. human-readable) files if > there are no ways to escape the keyword. > > - If SVN detects your non-binary file as binary (may happen with > non-Latin encodings), DO NOT SET fbsd:nokeywords but use fbsd:notbinary. > > - If SVN complains that a binary file does not have the keyword, first > try to set the correct mime-type (see below) and only set > fbsd:nokeywords if SVN still rejects the file. > > .css text/css > .dtd application/xml-dtd > .ent application/xml-dtd > .gif image/gif > .gz application/gzip > .html text/html > .ico image/vnd.microsoft.icon > .jpg image/jpeg > .js application/javascript > .log text/plain > .pdf application/pdf > .png image/png > .rss application/rss+xml > .sh text/plain > .svg image/svg+xml > .txt text/plain > .xml application/xml > .xsl application/xslt+xml > > If there are no objections, I'll give a sweep to the tree to make it > consistent and I'll document this. > > Gabor Sounds like a good thing to do to me. We should probably put this into the primer as well, so that for future files (of any extension) people can look up the correct keywords to set. Regards Benedict -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlCBSTEACgkQTSZQLkqBk0jmVwCgsi8eJz8uTk1NhSRqVWIwIZe1 S84AnjDFeVdD9s9I5I6K8K6iNmUSWQKx =e6ZN -----END PGP SIGNATURE-----