| 00:38.38 | *** join/#bzflag delusional (~delusiona@pool-100-6-16-124.pitbpa.fios.verizon.net) |
| 00:39.40 | *** join/#bzflag delusional (~delusiona@unaffiliated/delusional) |
| 02:01.52 | *** join/#bzflag I_Died_Once (~I_Died_On@unaffiliated/idiedonce/x-1828535) |
| 02:16.25 | *** join/#bzflag mdskpr_ (~quassel@li59-174.members.linode.com) |
| 02:16.41 | *** join/#bzflag mdskpr (~quassel@li59-174.members.linode.com) |
| 02:18.02 | *** join/#bzflag allejo (~allejo@li59-174.members.linode.com) |
| 02:18.02 | *** join/#bzflag allejo (~allejo@unaffiliated/allejo) |
| 02:46.23 | *** join/#bzflag I_Died_Once (~I_Died_On@unaffiliated/idiedonce/x-1828535) |
| 05:30.50 | *** join/#bzflag Pimpinella (~frank@gondolin.pimpi.org) |
| 07:23.12 | *** join/#bzflag zuii (~akos@BC06BD4B.catv.pool.telekom.hu) |
| 07:54.35 | *** join/#bzflag zuii (~akos@BC06BD4B.catv.pool.telekom.hu) |
| 10:50.33 | *** join/#bzflag Constitution (~josh@bzflag/developer/Constitution) |
| 11:04.14 | *** join/#bzflag Constitution (~josh@bzflag/developer/Constitution) |
| 11:05.36 | *** join/#bzflag rob1n (~rob1n@gateway/vpn/privateinternetaccess/rob1n) |
| 11:12.53 | *** join/#bzflag death__ (~I_Died_On@71.226.67.5) |
| 12:08.43 | *** join/#bzflag I_Died_Once (~I_Died_On@unaffiliated/idiedonce/x-1828535) |
| 17:24.24 | *** join/#bzflag Patlabor221 (~JeffM@12.167.61.45) |
| 17:24.34 | *** join/#bzflag Patlabor221 (~JeffM@unaffiliated/jeffm2501) |
| 17:24.34 | *** mode/#bzflag [+v Patlabor221] by ChanServ |
| 17:41.12 | *** join/#bzflag joevano (~joevano@bzflag/developer/JoeVano) |
| 17:41.12 | *** mode/#bzflag [+v joevano] by ChanServ |
| 17:48.17 | *** join/#bzflag _Bhoren (~quassel@2a01:e35:2eb9:21:59dd:3734:1813:fbf2) |
| 17:48.37 | *** join/#bzflag Bhoren (~quassel@2a01:e35:2eb9:21:59dd:3734:1813:fbf2) |
| 17:59.59 | *** join/#bzflag _Bhoren (~quassel@2a01:e35:2eb9:21:59dd:3734:1813:fbf2) |
| 18:29.38 | *** join/#bzflag joevano (~joevano@c-71-193-109-19.hsd1.in.comcast.net) |
| 18:30.27 | *** join/#bzflag zuii (~akos@BC06BD4B.catv.pool.telekom.hu) |
| 19:48.01 | *** join/#bzflag AAA_awright (~aaa@2607:5300:60:7d4::1) |
| 19:53.15 | *** join/#bzflag zuii (~akos@BC06BD4B.catv.pool.telekom.hu) |
| 19:56.13 | *** join/#bzflag zuii (~akos@BC06BD4B.catv.pool.telekom.hu) |
| 20:03.24 | *** join/#bzflag zuii1 (~akos@BC06BD4B.catv.pool.telekom.hu) |
| 20:05.52 | *** join/#bzflag zuii (~akos@BC06BD4B.catv.pool.telekom.hu) |
| 20:29.40 | *** join/#bzflag MarderIII (~marderii@enneman.demon.nl) |
| 20:49.53 | *** join/#bzflag zuii (~akos@BC06BD4B.catv.pool.telekom.hu) |
| 21:16.04 | *** join/#bzflag zuii (~akos@BC06BD4B.catv.pool.telekom.hu) |
| 21:29.05 | *** join/#bzflag zuii1 (~akos@BC06BD4B.catv.pool.telekom.hu) |
| 21:51.55 | *** join/#bzflag Bhoren (~quassel@2a01:e35:2eb9:21:45ff:e0fa:ac7f:39f6) |
| 22:08.20 | *** join/#bzflag joevano (~joevano@bzflag/developer/JoeVano) |
| 22:08.20 | *** mode/#bzflag [+v joevano] by ChanServ |
| 22:10.48 | BulletCatcher | Patlabor221: Do you want v2_99_shot_branch (svn name, AKA 2.99_server_shot_control in the import-5 GitHub repo) to have a Git tag name with a gsoc_ prefix along with gsoc_bzauthd, gsoc_irc, gsoc_libbzw, gsoc_server_collisions, and gsoc_server_listing? |
| 22:11.48 | Patlabor221 | yes |
| 22:12.00 | Patlabor221 | it didnt' start as SOC, but became SOC |
| 22:12.39 | BulletCatcher | will do |
| 22:22.04 | BulletCatcher | In import-5 I have the tips of never-released development branches 1.8, 2.99, 2.0_crystal_space, and 2.99_network_rewrite identified with Git tags and not Git branches to discourage further development on them (and to discourage "should I use it?" questions from contributors who look at the branch list and not the tags). |
| 22:22.09 | BulletCatcher | I left the abandoned release branches 1.7, 1.10, and 2.0 as proper Git branches. |
| 22:22.13 | BulletCatcher | Technically we can do it either way for any of these. |
| 22:22.15 | BulletCatcher | Do you have a preference? |
| 23:06.09 | Patlabor221 | I'm fine ether way |
| 23:06.20 | Patlabor221 | branches make sense, since we did release them at one point |
| 23:06.30 | Patlabor221 | and we'll make branches for future old versions |
| 23:06.33 | Patlabor221 | so it's fine |
| 23:07.02 | Patlabor221 | just FYI, I'll be in Germany starting tomorow untill the 21'st so my time's online will change. |
| 23:16.58 | *** join/#bzflag zuii (~akos@BC06BD4B.catv.pool.telekom.hu) |
| 23:21.39 | BulletCatcher | Have a good time! |
| 23:21.41 | BulletCatcher | Don't drink too much beer, too often, especially before driving fast on the Autobahn. |
| 23:23.58 | Patlabor221 | I'll be staying in frankfurt |
| 23:24.11 | Patlabor221 | they do applewine rather than beer |
| 23:28.37 | BulletCatcher | I'll leave the split between branches and tags as-is unless someone comes up with a convicing reason to change it. |
| 23:28.42 | BulletCatcher | Creating a new branch or a new tag in Git is easy. |
| 23:28.46 | BulletCatcher | It is only deleting, renaming, and similar destructive operations on branches and tags that require explicit corresponding manual action for each clone of the upstream repo. |
| 23:37.18 | BulletCatcher | For example, if we were to revive 2.99 development someone would just create a new 2.99 branch starting at the 2.99 tag (branches and tags are independent name spaces, so there can be one of each with the same name) and commit new changes as usual. |
| 23:37.29 | BulletCatcher | If we did that we would want to delete the 2.99 tag, but every developer with push access to our GitHub repo would have to do a "git tag -d 2.99" command on each of their repo clones or else they would push the tag back upstream the next time they did a "git push origin --tags" command. |