IRC log for #bzflag on 20170130

00:03.41*** join/#bzflag RoscoePColtrane (~flash@c-71-205-162-253.hsd1.co.comcast.net)
00:20.57BulletCatcherWorking safely in a throwaway repo clone, use "git subtree split" to extract a directory hierarchy and its history into disjoint branch.
00:21.01BulletCatcherThen use "git remote" commands to link that temporary repo to a temporary clone of the target repo (e.g., bzflag-tools) and copy the branch over.
00:21.03BulletCatcherAfter confirming that the target repo is correct, push upstream.
00:21.33BulletCatcherFinally, remove the hierarchy from the original repo.
00:23.21BulletCatcherOne of the awesome things about Git is that it is easy to do complicated unfamiliar tasks like that in repo clones that can be safely discarded if you screw up.
00:24.59BulletCatcherYou can script the whole process and put that script into Git, too, for future reference.
00:51.22*** join/#bzflag Shuist (~Shuist@ppp203-122-213-220.static.internode.on.net)
01:14.40*** join/#bzflag a_meteorite (~a_meteori@unaffiliated/ameteorite/x-000000001)
01:39.55macsformeafter doing that, do commits that touch files both inside and outside of that directory end up with new SHAs with just the changes within the target directory?
02:22.05allejowas PR #64 tested before it was merged in?
02:25.14*** join/#bzflag a_meteorite (~a_meteori@unaffiliated/ameteorite/x-000000001)
02:29.33blast007allejo: well, it compiled. I didn't write a plugin to test it.
02:29.50allejomeh
02:30.22allejoi probably should have updated the original issue, but clients send a drop flag message before a death message
02:30.52allejohttps://github.com/BZFlag-Dev/bzflag/blob/a7f17f522596dabc41f0c3ff6b427502eece1806/src/bzfs/bzfs.cxx#L3187-L3189
02:48.41blast007so, then it doesn't do anything?
02:48.51allejonope
02:49.01blast007yay
02:51.24allejothe if statement there will always return false since by the time bzfs handles the death, it's already thrown a dropped flag event
02:51.57BulletCatchermacsforme: after that process the original commits would remain unchanged in the source repo, so SHAs wouldn't change there.
02:51.58BulletCatcherThe destination branch would have new SHAs for the relevant commits.
02:56.08allejounless JeffM experienced otherwise, can we revert #64 or fix it?
03:10.50macsformesounds to me like it should be reverted
03:30.12JeffMallejo: I can fix it, I can use flag history
03:30.36allejo:o
03:30.55JeffMMore then than one way to skin a car
03:30.58JeffMCat
03:31.46allejowould timing be taken into account? i.e. a player drops a flag 30 seconds before they die
03:32.06JeffMYeah, I have an idea
03:32.20JeffMLast flag drop before an update
03:32.31JeffMIf I can't fix it then revert
03:32.43allejomkay :D
03:34.53JeffMOr revert it and I can redo the entire thing, whatever you want
03:36.58allejoi have no preference either way
03:39.21BulletCatcherWe can be patient if you think you can fix it.
03:39.33JeffMDoes the client send an update between the drop and the death?
03:40.38allejothat i'm not sure about, i'm not familiar with the client's code
03:40.46blast007it'd be a mix of TCP and UDP, right?
03:41.06blast007(the drop/death would be TCP and the player update UDP)
03:41.21blast007would that make it harder?
03:42.33JeffMWould it send one while dead?
03:43.38JeffMAlso, are all flags dropped? Also if the client drops the flag why does the server also drop it?
03:45.15allejo"just to be sure" i think
03:45.55JeffMK
03:46.22blast007Zombieland rule #2 - the double tap
05:58.03*** join/#bzflag BZnotify (~BZnotify@192.30.252.42)
05:58.03BZnotify[13bzflag] 15JeffM2501 opened pull request #66: Better implementation of flag on death PR 64 (062.4...062.4_killedflaghistory) 02https://git.io/vDTlq
05:58.03*** part/#bzflag BZnotify (~BZnotify@192.30.252.42)
05:58.22JeffMit checks to see if the last held flag has landed yet, so allejo can try that out to see if it fits his needs.
05:58.51JeffMit may not be prefect in all cases, but the API side will be the same once the proto is fixed, and some people will still have use for it's current behavor.
05:59.05JeffMif not, yank it
06:43.48allejoclones it
06:59.33allejoworks for me. should be a nice workaround until the behavior can be changed in 2.6
07:11.33*** join/#bzflag BZnotify (~BZnotify@192.30.252.42)
07:11.34BZnotify[13bzflag] 15allejo pushed 2 new commits to 062.4: 02https://git.io/vDTBd
07:11.34BZnotify13bzflag/062.4 14ae5fa3d 15JeffM2501: change the lastHeldFlag in the death message to be an ID...
07:11.34BZnotify13bzflag/062.4 14db0a06e 15Vladimir Jimenez: Merge pull request #66 from JeffM2501/2.4_killedflaghistory...
07:11.34*** part/#bzflag BZnotify (~BZnotify@192.30.252.42)
09:56.17*** join/#bzflag Shuist (~Shuist@ppp203-122-213-220.static.internode.on.net)
13:24.28tuponedoes premake support Installing file in a directory that is not the final one (aka DESTDIR)?
14:11.38macsformetupone: if you mean like the --prefix option, yes... but the premake script has to do it... it doesn't get passed onto the generated autotools scripts
14:23.26macsformehttps://github.com/macsforme/bzflag/commit/dfad14f5a4e36294405f6ab594f891ff6389df69
14:34.05*** join/#bzflag leny (~zuii@20014C4C1A619B00021E65FFFEDB9BF8.catv.pool.telekom.hu)
16:19.41JeffMallejo: I'm glad it worked out
16:20.51JeffMbranch deleted :)
16:41.02JeffMallejo: does that mean you can close issue #1?
16:42.52allejocould close it, i just reopened it to leave it as a note to fix 2.6 unless anyone feels it's unnecessary
16:43.12JeffMit would make sense to make that a different ticket that just talks about events, not the API
16:43.28JeffMsince the API will now work wiith ether logic flow
16:43.33JeffMIMHO
16:43.44JeffMsomeone fixing 2.6 will not have to change the API at all
17:55.34*** join/#bzflag Zehra (~Kanone@unaffiliated/zehra)
18:13.16tuponemacsforme: it is not prefix. you configure to run in prefix (e.g. /usr), but you install temporary in an empty directory. Then the package manager will get all the files in this temp directory and will packetisize (??)
18:13.35tuponetemporary directory is normall DESTDIR
18:41.36JeffMhappy birthday tupone  :)
18:47.13*** join/#bzflag a_meteorite (~a_meteori@unaffiliated/ameteorite/x-000000001)
19:03.56*** join/#bzflag a_meteorite (~a_meteori@unaffiliated/ameteorite/x-000000001)
19:26.55*** join/#bzflag a_meteorite (~a_meteori@unaffiliated/ameteorite/x-000000001)
19:35.05kierra~hapbir tupone
19:35.05infobotACTION sings a variant of Happy Birthday (to avoid royalty fees) to tupone
20:06.23blast007silly ibot, there are no royalty fees anymore
20:11.27kierraI guess there are more pressing matters to tend to than updating ibot :)
20:42.42JeffMI think singing to a european is terrorism now
20:50.27tuponeJeffM: thanks
20:52.25kierralol
20:53.01tuponethanks kierra too :)
20:54.06kierrayou are very welcome, enjoy your special day!
21:01.56Zehrait's actually interesting to note that there was a copyright on happy birthday
21:03.53Zehrait's probably the reason why in many movies another song instead of happy birthday was sung
21:05.16JeffMyes, it was only recently invalidated
21:05.36Zehraa judge ruled it was invalid for copyright iirc
21:06.15JeffMthere was a prior book it was published in that has gone into the PD, so the person making the copyright claim had the claim invalidated.
21:06.44Zehrathat's good
21:07.56Zehrakind of reminds me of some documents which would be nice to have
21:08.06Zehrabut are lost to history
21:47.10*** join/#bzflag disco-_ (~disco@unaffiliated/disco-)
22:32.53*** join/#bzflag mako (mako@2600:3c03::f03c:91ff:fe70:30aa)
22:42.39*** join/#bzflag Zehra (~Zehra@unaffiliated/zehra)
23:17.14*** join/#bzflag ukiki (ukiki@2600:3c03::f03c:91ff:fe70:30aa)
23:17.19*** part/#bzflag mako (mako@2600:3c03::f03c:91ff:fe70:30aa)
23:20.36*** part/#bzflag ukiki (ukiki@2600:3c03::f03c:91ff:fe70:30aa)
23:20.50*** join/#bzflag ukiki (ukiki@2600:3c03::f03c:91ff:fe70:30aa)
23:58.08*** join/#bzflag BulletCatcher (~bc@bzflag/developer/BulletCatcher)
23:58.08*** mode/#bzflag [+o BulletCatcher] by ChanServ
23:59.20*** mode/#bzflag [-o BulletCatcher] by ChanServ

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.