<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 18, 2016 at 3:12 PM, Michael Scherer <span dir="ltr"><<a href="mailto:mscherer@redhat.com" target="_blank">mscherer@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">Le mercredi 18 mai 2016 à 05:35 -0400, Prashanth Pai a écrit :<br>
> Hi all,<br>
><br>
> I tried out BFG tool on my github fork of glusterdocs project.<br>
><br>
> $ git count-objects -vH | grep size-pack<br>
> size-pack: 62.88 MiB<br>
><br>
> $ cd ..<br>
> $ java -jar bfg-1.12.12.jar --delete-files '*.{odp,pdf}' glusterdocs.git<br>
> $ cd glusterdocs.git<br>
> $ git reflog expire --expire=now --all && git gc --prune=now --aggressive<br>
><br>
> $ git count-objects -vH | grep size-pack<br>
> size-pack: 2.52 MiB<br>
><br>
> As seen above, the repo size was reduced from around 62MB to 2.5MB.<br>
><br>
> Caveat:<br>
> If we do go with this approach, as git history is re-written, every<br>
> contributor will have to re-fork the "cleaned" repo. There are about<br>
> 60 forks now on github. Consequently, anyone sending a PR will now<br>
> have to create a fresh clone.<br>
><br>
> Is this "reset" worth it given the slight confusion and one-time<br>
> inconvenience to contributors ? Thoughts ?<br>
<br>
</span>I would vote +1. Having too much binary is a pain.<br>
<br>
Alternatively, we can make a 2nd repo after clean-up, and direct people<br>
to the new repo, it would be less pain (cause you just fork once, no<br>
need to do complicated git stuff, or remove the repo to fork again on<br>
github, especially since github ask to confirm and stuff before removing<br>
a repo)<br>
<span class="HOEnZb"><font color="#888888">--<br>
Michael Scherer<br>
Sysadmin, Community Infrastructure and Platform, OSAS<br>
<br></font></span></blockquote><div><br></div><div>All in favor of the 'everyone working on this should clone again' approach. </div><div>- amye </div><div><br></div></div><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">Amye Scavarda | <a href="mailto:amye@redhat.com" target="_blank">amye@redhat.com</a> | Gluster Community Lead</div></div>
</div></div>