>From: Pierre Schmitz <pie...@archlinux.de> >To: internals@lists.php.net >Cc: >Date: Sat, 25 May 2013 05:48:07 +0200 >Subject: Re: [PHP-DEV] Re: About fileinfo test.mp3 >Am 24.05.2013 23:38, schrieb Anatol Belski: >> Hi David, >> >> On Fri, 2013-05-24 at 23:28 +0200, David Soria Parra wrote: >>> Hi Anatol, >>> >>> I saw your commit 74555e7c26b2c61bb8e67b7d6a6f4d2b8eb3a5f3 added a 4mb >>> mp3 file. Is it possible to create a much smaller mp3 that helps to >>> reproduce the same bug? The file blows up the taball file for the final >>> release, which I hope to keep as small as possible. >>> >>> Thanks in advance, >>> David >> >> yep, I'm working on that currently. That file was additionally reported >> as containing some copyrighted song. Never looked inside though :) . >> I'll fix that at least by tomorrow. >> >> Regards >> >> Anatol > >Hi, > >is there a sane way to completely remove that file from the git history? >Having a public git mirror might get me into trouble and I am probably >not the only one. > >Also: WTF? > >Greetings, > >Pierre > >
Gitub has a nice write at https://help.github.com/articles/remove-sensitive-data The short sort is that to remove it from the history you need to apply 'git rm' as a filter-branch to your repo. Two items of note, anyone that has pulled will have to rebase and if you really want it removed (no direct access even with the commit's SHA1 key), the remote can't be updated with a push. It will have to deleted and replaced with a repo that was updated with the filter-branch. Also note that this may effect tagging. Walter -- The greatest dangers to liberty lurk in insidious encroachment by men of zeal, well-meaning but without understanding. -- Justice Louis D. Brandeis -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
