migration of subversion to parrot.org

Mark Glines mark at glines.org
Thu Jan 15 14:55:59 UTC 2009


chromatic wrote:
> On Saturday 17 January 2009 10:08:29 Mark Glines wrote:
> 
>> As I understand it, the svn properties
>> used by parrot just tell svn to rewrite things like $Id$ (which git-svn
>> doesn't bother to do), and to use native line endings for text files
>> (which git-svn also might not bother to do).  Hmm.  It's possible to
>> work easily without the former, but development on various platforms
>> might get bitten by the latter.  (I haven't tested it, but it sounds
>> problematic.)
> 
> It's not.  It's really, really not.  I've asked multiple times for anyone to 
> tell me for which files it's problematic.

Confirmed.  In the IRC channel last night, Casan++ grabbed a copy of
msysgit on win32 and cloned my mirror of the parrot sources.  He was
able to open source files in notepad just fine, which shows that msysgit
created the files with native line-endings.  Thus, it's a non-issue.

Mark


More information about the parrot-dev mailing list