- From: himorin / Atsushi Shimono via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Feb 2025 12:29:03 +0000
- To: public-i18n-archive@w3.org
> Thanks [@xfq](https://github.com/xfq), I've contacted [@himorin](https://github.com/himorin) and asked him to delete the image source files that are on Git LFS. Hopefully, this should solve the issue. sorry I could not reply to the thread yet, but I don't think just deleting from HEAD would not work, since all remains in git history. it's quite hard and will take several work days to go through all git history to remove every entry, since there should be mix between lfs manipulation and normal edits, but I don't have any knowledge nor experience to remove historical GIT LFS entries. also I am quite in doubt, and also I've already stated several times like last time of this discussion, we should be better to identify what is the exact operation eating LFS bandwidth, since normal or simple 'git clone' or 'git checkout' will not download any of LFS data itself (but just pointer within git repository), and definitely something should happen to eat allowed bandwidth. I'm not quite sure why we are just going just to remove LFS objects just from the HEAD, but without diving into seeking the root cause... (not objecting to do the operation, but I just could not believe just removing will resolve this...) -- GitHub Notification of comment by himorin Please view or discuss this issue at https://github.com/w3c/jlreq/issues/454#issuecomment-2650678533 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 11 February 2025 12:29:04 UTC