| 00:32.27 | *** join/#bzflag spldart (~spldart@172.56.15.125) |
| 00:32.27 | *** join/#bzflag spldart (~spldart@bzflag/contributor/spldart) |
| 00:32.27 | *** mode/#bzflag [+v spldart] by ChanServ |
| 00:44.44 | *** join/#bzflag khonkhortisan1 (~Kyle@c-24-16-240-200.hsd1.wa.comcast.net) |
| 00:55.24 | *** join/#bzflag khonkhortisan (~Kyle@c-24-16-240-200.hsd1.wa.comcast.net) |
| 01:05.50 | *** join/#bzflag khonkhortisan1 (~Kyle@c-24-16-240-200.hsd1.wa.comcast.net) |
| 01:08.08 | *** join/#bzflag Shuist (~Shuist@ppp203-122-213-220.static.internode.on.net) |
| 01:11.44 | *** join/#bzflag Pimpi_ (~frank@pD9E1175D.dip0.t-ipconnect.de) |
| 03:46.55 | *** join/#bzflag DTRemenak (~DTRemenak@cpe-172-112-1-125.socal.res.rr.com) |
| 03:46.55 | *** join/#bzflag DTRemenak (~DTRemenak@about/essy/CrazyCoder/DTRemenak) |
| 03:46.55 | *** mode/#bzflag [+v DTRemenak] by ChanServ |
| 04:35.52 | *** part/#bzflag BulletCatcher (~bc@bzflag/developer/BulletCatcher) |
| 04:43.48 | *** join/#bzflag FastLizard4 (fastlizard@wikipedia/pdpc.active.FastLizard4) |
| 04:47.05 | *** join/#bzflag BulletCatcher (~bc@bzflag/developer/BulletCatcher) |
| 06:17.06 | *** join/#bzflag I_Died_Once (~I_Died_On@2601:902:c002:887c:8b9:b92d:4c1e:75b6) |
| 06:17.06 | *** join/#bzflag I_Died_Once (~I_Died_On@unaffiliated/idiedonce/x-1828535) |
| 06:27.38 | *** join/#bzflag I_Died_Once (~I_Died_On@unaffiliated/idiedonce/x-1828535) |
| 06:36.20 | *** join/#bzflag the_map (~the_map@unaffiliated/the-map/x-1795707) |
| 10:20.47 | *** join/#bzflag Constitution (~josh@bzflag/developer/Constitution) |
| 10:43.03 | *** join/#bzflag zuii (~akos@BC06BF93.catv.pool.telekom.hu) |
| 11:14.21 | *** join/#bzflag zuii (~akos@belso.ii.hu) |
| 12:31.46 | *** join/#bzflag zuii (~akos@BC06BF93.catv.pool.telekom.hu) |
| 13:23.20 | *** join/#bzflag zui (~akos@belso.ii.hu) |
| 15:56.47 | *** join/#bzflag dngor (~abuse@p3m/dngor) |
| 17:19.06 | *** join/#bzflag dngor (~abuse@p3m/dngor) |
| 17:58.43 | *** join/#bzflag zuii (~akos@BC06BF93.catv.pool.telekom.hu) |
| 18:45.35 | *** join/#bzflag Shuist (~Shuist@ppp203-122-213-220.static.internode.on.net) |
| 19:35.25 | *** join/#bzflag dngor (~abuse@p3m/dngor) |
| 19:46.35 | *** join/#bzflag DTRemenak (~DTRemenak@about/essy/CrazyCoder/DTRemenak) |
| 19:46.35 | *** mode/#bzflag [+v DTRemenak] by ChanServ |
| 20:29.15 | *** join/#bzflag zui (~akos@BC06BF93.catv.pool.telekom.hu) |
| 21:00.56 | *** join/#bzflag rob1n (Nomsayinth@unaffiliated/rob1n) |
| 22:01.10 | *** join/#bzflag zuii (~akos@BC06BF93.catv.pool.telekom.hu) |
| 22:26.24 | *** join/#bzflag khonkhortisan (~Kyle@c-24-16-240-200.hsd1.wa.comcast.net) |
| 23:09.37 | khonkhortisan | Suppose I had two features that were all tested and ready to add to bzflag, where both require a protocol change, but bzflag itself isn´t ready for the next protocol. Where would I put them? One base branch that just has a protocol change, two feature branches based on that (which share the same protocol but are incompatible, for testing separately), then another beta testing branch based on top of both of those? (as the preview fo |
| 23:13.26 | blast007 | protocol changes can go into master |
| 23:13.46 | blast007 | what features are they? |
| 23:18.02 | khonkhortisan | I don´t have any right now, but how would that work? Add them one at a time, each with a protocol change, or only add one protocol change to make it different from 2.4, then add the features? And is there any time to not add a protocol-chnaging feature? |
| 23:19.46 | khonkhortisan | I´m just wondering if a feature would get slowed down from being included just because it changed the protocol, compared to a feature that didn´t. |
| 23:20.05 | blast007 | there's not a 'yes or no' answer to that :) |