Backward compatible LEGACY_LOG_NAMES default

Bug #285637 reported by Luke-Jr
2
Affects Status Importance Assigned to Milestone
Armagetron Advanced
Fix Committed
Medium
Yann Kaiser

Bug Description

The current default of LEGACY_LOG_NAMES=0 will break any upgrades from 0.2.8.2.1 where the ladderlog isn't completely ignored. Since 0.2.8.2.1 to 0.2.8.3 is supposed to be a compatible upgrade, 0.2.8.* should have a default value of LEGACY_LOG_NAMES=1.

Revision history for this message
Yann Kaiser (epsy) wrote :

I would suggest it to be defaulted to 1 only for non-armathenticating builds

Revision history for this message
Yann Kaiser (epsy) wrote :

Done in r907.

Changed in armagetronad:
assignee: nobody → epsy
importance: Undecided → Medium
status: New → Fix Committed
Revision history for this message
Yann Kaiser (epsy) wrote : Re: [Bug 285637] [NEW] Backward compatible LEGACY_LOG_NAMES default

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

 milestone 0.2.8.3
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkkE+scACgkQ0+psVkkaewf6aQCbBsF3ehaspwpR4/webNlAo0SN
ch0An2+ZZ3U4GZKvJiFaeVHnT95ohFhK
=MIKd
-----END PGP SIGNATURE-----

Changed in armagetronad:
milestone: none → 0.2.8.3
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.