Bad working tree format branching smart server for content filtering

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Frits Jalvingh wrote:
> Hello,
> 
> I'm in the process of converting our repositories to use CRLF content 
> filtering this weekend but I'm running into trouble again. I tested this using 
> simple transports and all goes well; when I branch a repo I get a new repo 
> using WorkingTreeFormat5:
> 
> Format:
>        control: Meta directory format 1
>   working tree: Working tree format 5
>         branch: Branch format 7
>     repository: Packs 6 rich-root (uses btree indexes, requires bzr 1.9)
> 
> which is OK for content filtering. But when I branch off a bzr 1.16.1 smart 
> server I get a WorkingTreeFormat4:
> 
> Format:
>        control: Meta directory format 1
>   working tree: Working tree format 4
>         branch: Branch format 7
>     repository: Packs 6 rich-root (uses btree indexes, requires bzr 1.9)
> 
> which is NOT OK for content filtering (and consequently the tree created has 
> incorrect line endings). 
> 
> Is there someplace where the default working tree format can be set? If 
> necessary by patching bzr?
> 
> Frits
> 
> 

Put this in a .py file in your plugin path (eg,
  ~/.bazaar/plugins/wt_default.py):

from bzrlib import workingtree, workingtree_4
workingtree.WorkingTreeFormat.set_default_format(
	workingtree.WorkingTreeFormat.get(
		workingtree_4.WorkingTreeFormat.get_format_string()))

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkpSBBsACgkQJdeBCYSNAAOnvACfQgAUAxcUf5J486uGb/tlbf3v
2JkAoJVxGzM5r1cEbqhWhczgrf7kyzS9
=2K7C
-----END PGP SIGNATURE-----