à la con
- 0 Posts
- 10 Comments
drre@feddit.orgto
Technology@lemmy.world•I analyzed 200 e-commerce sites and found 73% of their traffic is fakeEnglish
11·2 months agoreally interesting article. thanks a lot for sharing
hello wildcats
drre@feddit.orgto
Technology@lemmy.world•YouTube removes 'gender identity' from hate speech policyEnglish
2·9 months agoabsolutely agree. i just wanted to point out that not everything has to be a video
drre@feddit.orgto
Technology@lemmy.world•YouTube removes 'gender identity' from hate speech policyEnglish
95·9 months agototally agree with reading more. text is easy to consume, easy to store, (somewhat) easy to verify (if sources are provided), and it keeps (if using dead trees for storage). ever since the pandemic i started reading more and must say i really like it
happy hardcore
thanks for the reply, but i think i got that. from the linked article:
For example, if you changed repo/packages/foo/CHANGELOG.json, when git was getting ready to do the push, it was generating a diff against repo/packages/bar/CHANGELOG.json! This meant we were in many occasions just pushing the entire file again and again, which could be 10s of MBs per file in some cases, and you can imagine in a repo our size, how that would be a problem.
but wouldn’t these erroneous diffs not show up in
git diff? it seems that they were pushing (maybe automatically?)without inspecting the diffs first
maybe I’m missing something but wouldn’t this show up in a diff before pushing?


love the reference