wesnoth-dev  

Messages by Thread

• • Re: [Wesnoth-dev] AI is not in a releasable state Ignacio Morelle
  • Re: [Wesnoth-dev] AI is not in a releasable state David White
  • Re: [Wesnoth-dev] AI is not in a releasable state Eric S. Raymond
  • Re: [Wesnoth-dev] AI is not in a releasable state Eric S. Raymond
  • Re: [Wesnoth-dev] AI is not in a releasable state John McNabb
  • Re: [Wesnoth-dev] AI is not in a releasable state John McNabb
  • Re: [Wesnoth-dev] AI is not in a releasable state Guillaume Melquiond
  • Re: [Wesnoth-dev] AI is not in a releasable state Bruno Wolff III
  • Re: [Wesnoth-dev] AI is not in a releasable state Eric S. Raymond
  • Re: [Wesnoth-dev] AI is not in a releasable state Eric S. Raymond
  • Re: [Wesnoth-dev] AI is not in a releasable state David White
  • Re: [Wesnoth-dev] AI is not in a releasable state Nils Kneuper
  • Re: [Wesnoth-dev] AI is not in a releasable state Fabian Mueller
  • Re: [Wesnoth-dev] AI is not in a releasable state Nils Kneuper
  • Re: [Wesnoth-dev] AI is not in a releasable state Eric S. Raymond
  • Re: [Wesnoth-dev] AI is not in a releasable state Eric S. Raymond
  • Re: [Wesnoth-dev] AI is not in a releasable state Greg Boggs
  • Re: [Wesnoth-dev] AI is not in a releasable state Nils Kneuper
  • Re: [Wesnoth-dev] AI is not in a releasable state Greg Boggs
  • Re: [Wesnoth-dev] AI is not in a releasable state Eric S. Raymond
  • Re: [Wesnoth-dev] AI is not in a releasable state Eric S. Raymond
• Re: [Wesnoth-dev] [bug #13118] Risk of OOS with hidden units Jörg Hinrichs
  • Re: [Wesnoth-dev] [bug #13118] Risk of OOS with hidden units Jörg Hinrichs
  • Re: [Wesnoth-dev] [bug #13118] Risk of OOS with hidden units Jörg Hinrichs
  • Re: [Wesnoth-dev] [bug #13118] Risk of OOS with hidden units John McNabb
  • Re: [Wesnoth-dev] [bug #13118] Risk of OOS with hidden units Jörg Hinrichs
  • Re: [Wesnoth-dev] [bug #13118] Risk of OOS with hidden units Ali
  • Re: [Wesnoth-dev] [bug #13118] Risk of OOS with hidden units Jörg Hinrichs
  • Re: [Wesnoth-dev] [bug #13118] Risk of OOS with hidden units Mark de Wever
• Re: [Wesnoth-dev] possible security problems (eg with current python implementation) Patrick Parker
  • Re: [Wesnoth-dev] possible security problems (eg with current python implementation) Cameron J. Morland
  • Re: [Wesnoth-dev] possible security problems (eg with current python implementation) Sergey Popov
  • Re: [Wesnoth-dev] possible security problems (eg with current python implementation) allefant
  • Re: [Wesnoth-dev] possible security problems (eg with current python implementation) Greg Copeland
  • Re: [Wesnoth-dev] possible security problems (eg with current python implementation) dave
  • [Wesnoth-dev] Scripting in the longer term (was: Re: possible security problems) Eric S. Raymond
• [Wesnoth-dev] registered at freenode, now wesnoth cloaks available Nils Kneuper
  • Re: [Wesnoth-dev] registered at freenode, now wesnoth cloaks available jeremy rosen
  • Re: [Wesnoth-dev] registered at freenode, now wesnoth cloaks available Nils Kneuper
  • Re: [Wesnoth-dev] registered at freenode, now wesnoth cloaks available Nils Kneuper
• [Wesnoth-dev] Informing about a change... Mario Rodrÿffffedguez
• [Wesnoth-dev] more private IRC chan for security related discussions Nils Kneuper
• [Wesnoth-dev] possible security problems (eg with current python implementation) Nils Kneuper
  • Re: [Wesnoth-dev] possible security problems (eg with current python implementation) Mark de Wever
  • Re: [Wesnoth-dev] possible security problems (eg with current python implementation) allefant
  • Re: [Wesnoth-dev] possible security problems (eg with current python implementation) jeremy rosen
  • Re: [Wesnoth-dev] possible security problems (eg with current python implementation) David White
  • Re: [Wesnoth-dev] possible security problems (eg with current python implementation) Daniel Franke
  • Re: [Wesnoth-dev] possible security problems (eg with current python implementation) Greg Copeland
  • Re: [Wesnoth-dev] possible security problems (eg with current python implementation) David Philippi
  • Re: [Wesnoth-dev] possible security problems (eg with current python implementation) jeremy rosen
  • Re: [Wesnoth-dev] possible security problems (eg with current python implementation) Nils Kneuper
  • Re: [Wesnoth-dev] possible security problems (eg with current python implementation) Sergey Popov
  • Re: [Wesnoth-dev] possible security problems (eg with current python implementation) Mark de Wever
  • Re: [Wesnoth-dev] possible security problems (eg with current python implementation) allefant
  • Re: [Wesnoth-dev] possible security problems (eg with current python implementation) Greg Copeland
  • Re: [Wesnoth-dev] possible security problems (eg with current python implementation) dave
  • Re: [Wesnoth-dev] possible security problems (eg with current python implementation) Daniel Franke
  • Re: [Wesnoth-dev] possible security problems (eg with current python implementation) dave
  • Re: [Wesnoth-dev] possible security problems (eg with current python implementation) allefant
  • Re: [Wesnoth-dev] possible security problems (eg with current python implementation) Greg Copeland
  • Re: [Wesnoth-dev] possible security problems (eg with current python implementation) Greg Copeland
  • Re: [Wesnoth-dev] possible security problems (eg with current python implementation) Mark de Wever
• [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Mark de Wever
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Eric S. Raymond
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Mark de Wever
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Sergey Popov
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Mark de Wever
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Sergey Popov
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Mark de Wever
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Sergey Popov
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Mark de Wever
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Sergey Popov
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Alexander Neundorf
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Sergey Popov
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Alexander Neundorf
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Sergey Popov
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Alexander Neundorf
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Alexander Neundorf
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Sergey Popov
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) allefant
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Mark de Wever
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Guillaume Melquiond
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Nils Kneuper
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Guillaume Melquiond
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Nils Kneuper
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Guillaume Melquiond
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Mark de Wever
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Bruno Wolff III
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Mark de Wever
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Alexander Neundorf
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Mark de Wever
  • Re: [Wesnoth-dev] build system evaluation (autotools/cmake/scons) Daniel Franke
• [Wesnoth-dev] Transparent portraits are cool Bruno Wolff III
• [Wesnoth-dev] Updated 1.6 release plan Nils Kneuper
  • Re: [Wesnoth-dev] Updated 1.6 release plan Eric S. Raymond
  • Re: [Wesnoth-dev] Updated 1.6 release plan Mark de Wever
• Re: [Wesnoth-dev] [Wesnoth-commits] r32813 - in /trunk: changelog players_changelog src/game_preferences_display.cpp src/preferences.cpp Bruno Wolff III
  • Re: [Wesnoth-dev] [Wesnoth-commits] r32813 - in /trunk: changelog players_changelog src/game_preferences_display.cpp src/preferences.cpp Mark de Wever
  • Re: [Wesnoth-dev] [Wesnoth-commits] r32813 - in /trunk: changelog players_changelog src/game_preferences_display.cpp src/preferences.cpp Bruno Wolff III
• [Wesnoth-dev] GSOC 2009 let's get the ball rolling jeremy rosen
  • Re: [Wesnoth-dev] GSOC 2009 let's get the ball rolling Mark de Wever
  • Re: [Wesnoth-dev] GSOC 2009 let's get the ball rolling Nils Kneuper
• [Wesnoth-dev] GCC 4.4 Bruno Wolff III
  • Re: [Wesnoth-dev] GCC 4.4 Guillaume Melquiond
  • Re: [Wesnoth-dev] GCC 4.4 Mark de Wever
  • Re: [Wesnoth-dev] GCC 4.4 Bruno Wolff III
  • Re: [Wesnoth-dev] GCC 4.4 Bruno Wolff III
  • Re: [Wesnoth-dev] GCC 4.4 Bruno Wolff III
  • Re: [Wesnoth-dev] GCC 4.4 Mark de Wever
  • Re: [Wesnoth-dev] GCC 4.4 Bruno Wolff III
  • Re: [Wesnoth-dev] GCC 4.4 Bruno Wolff III
  • Re: [Wesnoth-dev] GCC 4.4 Guillaume Melquiond
  • Re: [Wesnoth-dev] GCC 4.4 Bruno Wolff III
  • Re: [Wesnoth-dev] GCC 4.4 Bruno Wolff III
  • Re: [Wesnoth-dev] GCC 4.4 Bruno Wolff III
  • Re: [Wesnoth-dev] GCC 4.4 Mark de Wever
  • Re: [Wesnoth-dev] GCC 4.4 Guillaume Melquiond
• [Wesnoth-dev] Pre-1.6 string fixes, and a script to make them painless Eric S. Raymond
• Re: [Wesnoth-dev] [Wesnoth-commits] r32504 - /trunk/src/image_function.hpp David Philippi
  • Re: [Wesnoth-dev] [Wesnoth-commits] r32504 - /trunk/src/image_function.hpp Ignacio Morelle
• [Wesnoth-dev] Approaching 1.6 and some other stuff... (planned release of 1.5.9, feature freeze, GSoC, FOSDEM, ...) Nils Kneuper
  • Re: [Wesnoth-dev] Approaching 1.6 and some other stuff... (planned release of 1.5.9, feature freeze, GSoC, FOSDEM, ...) Nils Kneuper
• [Wesnoth-dev] Wesnoth and LUA Guillaume Melquiond
  • Re: [Wesnoth-dev] Wesnoth and LUA Mark de Wever
  • Re: [Wesnoth-dev] Wesnoth and LUA jeremy rosen
  • Re: [Wesnoth-dev] Wesnoth and LUA Guillaume Melquiond
  • Re: [Wesnoth-dev] Wesnoth and LUA David White
• [Wesnoth-dev] FOSDEM 2009 discussions jeremy rosen
• Re: [Wesnoth-dev] summary upload Nils Kneuper
  • Re: [Wesnoth-dev] summary upload Bruno Wolff III
  • Re: [Wesnoth-dev] summary upload allefant
  • Re: [Wesnoth-dev] summary upload Bruno Wolff III
  • Re: [Wesnoth-dev] summary upload cib
• [Wesnoth-dev] Wesnoth refactoring and future direction plan Ivan Illarionov
  • Re: [Wesnoth-dev] Wesnoth refactoring and future direction plan John McNabb
  • Re: [Wesnoth-dev] Wesnoth refactoring and future direction plan Ivan Illarionov
  • Re: [Wesnoth-dev] Wesnoth refactoring and future direction plan Greg Copeland
  • Re: [Wesnoth-dev] Wesnoth refactoring and future direction plan Eric S. Raymond
  • Re: [Wesnoth-dev] Wesnoth refactoring and future direction plan Ivan Illarionov
  • Re: [Wesnoth-dev] Wesnoth refactoring and future direction plan Mark de Wever
  • Re: [Wesnoth-dev] Wesnoth refactoring and future direction plan Ivan Illarionov
  • Re: [Wesnoth-dev] Wesnoth refactoring and future direction plan Mark de Wever
  • Re: [Wesnoth-dev] Wesnoth refactoring and future direction plan Greg Copeland
  • Re: [Wesnoth-dev] Wesnoth refactoring and future direction plan Alexander Neundorf
  • Re: [Wesnoth-dev] Wesnoth refactoring and future direction plan Greg Copeland
  • Re: [Wesnoth-dev] Wesnoth refactoring and future direction plan dave
• [Wesnoth-dev] Open lwetter to Ivan Illarionov Eric S. Raymond
  • Re: [Wesnoth-dev] Open lwetter to Ivan Illarionov Ivan Illarionov
  • Re: [Wesnoth-dev] Open lwetter to Ivan Illarionov Eric S. Raymond
• Re: [Wesnoth-dev] [Wesnoth-commits] r31950 - in /branches/1.4: changelog po/wesnoth-aoi/ja.po po/wesnoth-l/ja.po po/wesnoth-sof/ja.po po/wesnoth-utbs/ja.po Nils Kneuper
• [Wesnoth-dev] Up and down arrow behaviour in MP dialog Mark de Wever
  • Re: [Wesnoth-dev] Up and down arrow behaviour in MP dialog jeremy rosen
  • Re: [Wesnoth-dev] Up and down arrow behaviour in MP dialog Mark de Wever
• [Wesnoth-dev] 1.7 design direction and the great Python shift Eric S. Raymond
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift jeremy rosen
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Eric S. Raymond
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift David White
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Eric S. Raymond
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Ivan Illarionov
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift David White
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Rusty Russell
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift jeremy rosen
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Ivan Illarionov
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Ivan Illarionov
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Ivan Illarionov
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Mark de Wever
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Mark de Wever
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Alexander Neundorf
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Mark de Wever
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Martin Renold
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift David White
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Eric S. Raymond
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Eric S. Raymond
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Mark de Wever
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Sergey Popov
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift David White
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Eric S. Raymond
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift David White
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Eric S. Raymond
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift David White
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Mark de Wever
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Eric S. Raymond
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Mark de Wever
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Sergey Popov
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Greg Copeland
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Arc Riley
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift David Philippi
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Arc Riley
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Ivan Illarionov
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Arc Riley
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Richard Kettering III
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Greg Copeland
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift allefant
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Martin Renold
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Ivan Illarionov
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift David White
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift cib
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift David White
  • Re: [Wesnoth-dev] 1.7 design direction and the great Python shift Eric S. Raymond

• Earlier messages
• Later messages