makmarian@fedia.io to Open Source@lemmy.ml · vor 1 JahrWinampDesktop/winamp - Licence violates github TOS · Issue #6github.comexternal-linkmessage-square54linkfedilinkarrow-up1141arrow-down11cross-posted to: foss@beehaw.org
arrow-up1140arrow-down1external-linkWinampDesktop/winamp - Licence violates github TOS · Issue #6github.commakmarian@fedia.io to Open Source@lemmy.ml · vor 1 Jahrmessage-square54linkfedilinkcross-posted to: foss@beehaw.org
minus-squaredjangolinkfedilinkEnglisharrow-up19·vor 1 JahrOmg, gotta clone the repo, before they remove it. 😂
minus-squaretheshatterstone54@feddit.uklinkfedilinkarrow-up10·vor 1 JahrCurrently still in history. Issue was closed an hour ago so u don’t have long. Hurry
minus-squarechebra@mstdn.iolinkfedilinkarrow-up6·vor 1 Jahr@theshatterstone54 @django done, but be advised, it’s 2.7GB
minus-squaredjangolinkfedilinkEnglisharrow-up9·vor 1 JahrGot a copy now as well. As they appear to be still confused about git, others might still have a chance. 😂
minus-squarechebra@mstdn.iolinkfedilinkarrow-up1·vor 1 Jahr@django I see a force-push 22 minutes ago, do you see a “removed it” commit in the history?
minus-squaredjangolinkfedilinkEnglisharrow-up3·vor 1 Jahrstill part of the repo though: https://github.com/WinampDesktop/winamp/tree/3ab19235a69d96ba0d3d3d32428ea6e7afef6478/Src/Plugins/DSP/sc_serv3
minus-squarechebra@mstdn.iolinkfedilinkarrow-up2·vor 1 Jahr@django until it’s garbage-collected. All commits changed IDs, even the ones from yesterday.
minus-squaredjangolinkfedilinkEnglisharrow-up2·vor 1 JahrI can just create a branch in my local clone
minus-squarechebra@mstdn.iolinkfedilinkarrow-up1·vor 1 Jahr@django TIL: dangling commits shouldn’t be downloaded by git clone, UNLESS they are referenced by forks which makes them probably not-really-dangling, and github doesn’t clean them automatically, Jef would have to ask Github support: https://stackoverflow.com/questions/4367977/how-to-remove-a-dangling-commit-from-github
Omg, gotta clone the repo, before they remove it. 😂
Currently still in history. Issue was closed an hour ago so u don’t have long. Hurry
@theshatterstone54 @django
done, but be advised, it’s 2.7GB
Got a copy now as well. As they appear to be still confused about git, others might still have a chance. 😂
@django I see a force-push 22 minutes ago, do you see a “removed it” commit in the history?
still part of the repo though: https://github.com/WinampDesktop/winamp/tree/3ab19235a69d96ba0d3d3d32428ea6e7afef6478/Src/Plugins/DSP/sc_serv3
@django until it’s garbage-collected. All commits changed IDs, even the ones from yesterday.
I can just create a branch in my local clone
@django
TIL: dangling commits shouldn’t be downloaded by git clone, UNLESS they are referenced by forks which makes them probably not-really-dangling, and github doesn’t clean them automatically, Jef would have to ask Github support: https://stackoverflow.com/questions/4367977/how-to-remove-a-dangling-commit-from-github