+ [2019-10-29T18:38:38Z] Atlenohen Why does github diff compare forks to the upstream master in a weird way?
+ [2019-10-29T18:40:42Z] Atlenohen The repo started out with commit123 and for some reason it has a few changes from commit130 ... the upstream master is on commit250, but when comparing those rougue changes are included in the comparison, so it's showing that it's removing what's already been removed.
+ [2019-10-29T18:40:43Z] R2robot weird is the new normal.
+ [2019-10-29T18:41:22Z] FrankyCyborg abort, continue, abort, continue ... this download reminds me of the 90s and modem speeds at 14.4 KB/sec =)
+ [2019-10-29T18:41:51Z] Atlenohen Looking at git log the repo never updated past commit123, somehow the developer (who had a lot of VS bugs, etc) managed to get a file in from a higher commit, which now messes up diffs, will a rebase fix this?

message no. 175474

Posted by tychotithonus in #github at 2019-10-29T13:41:21Z

jhass: indeed. i shotgunned the issue through a few different channels, assuming it's esoteric enough that it's going to take a while to bubble up to the right team
+ [2019-10-30T10:00:50Z] bello hi my friends. i'm curious if i may use github to upload bundle files to share with my friends for their install?
+ [2019-10-30T10:53:55Z] R2robot what kind of files?
+ [2019-10-30T10:59:45Z] bello bundle installation
+ [2019-10-30T11:00:29Z] bello includes set up zip phyton and json xml files
+ [2019-10-30T11:03:12Z] R2robot if they're in your repo