Mailing-List: contact general-help@gump.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Gump code and data" <general@gump.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Date: Tue, 14 Dec 2004 21:31:26 +1100
From: David Crossley <crossley@apache.org>
To: Gump code and data <general@gump.apache.org>
Subject: native line-endings (Was: svn commit: r111800 -
 /gump/trunk/python/gump/core/model/project.py)
Message-ID: <20041214103111.GA18526@igg.indexgeo.com.au>
References: <20041214095917.88999.qmail@minotaur.apache.org>
 <m3mzwhgpgu.fsf@bodewig.bost.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <m3mzwhgpgu.fsf@bodewig.bost.de>
User-Agent: Mutt/1.4i

Stefan Bodewig wrote:
> This change looks far bigger than it actually was because of line-end
> tranformations.  I vaguely recall there is a property we should add to
> the auto-props so that all *.py files are assumed to have platform
> specific line-feeds by SVN, but I've lost the details right now.

* Make sure that the file has the proper line endings
  for whatever operating system you are on.
* svn add myfile.txt
* svn propset svn:eol-style native myfile.txt

You can configure your svn client to do it automatically.
We created a config file at Forrest:
http://issues.cocoondev.org/browse/FOR-124

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org