Bug#908678: Testing the filter-branch scripts
On 2018-11-13 18:14:54, Daniel Lange wrote:
>> The Python job finished successfully here after 10 hours.
> 6h40 mins here as I ported your improved logic to the python2 version :).
>
> # git filter-branch --tree-filter '/usr/bin/python2 /split-by-year.pyc' HEAD
> Rewrite 1169d256b27eb7244273671582cc08ba88002819 (68356/68357) (24226 seconds passed, remaining 0 predicted)
> Ref 'refs/heads/master' was rewritten
>
> The tree-filter blows up the .git/objects store to 13G though.
> But nothing a git gc can't fix.
Ah but that's because the old repository is still in there. You need to
clone the repo in a clean copy:
git clone file://$PWD/security-tracker security-tracker-filtered
To get the minimal version, i even did that twice although I'm not sure
that's necessary.
[...]
>> I looked at splitting that file per CVE. That did not scale and just
>> created new problems. But splitting by *year* seems like a very
>> efficient switch, and I think it would be worth pursuing that idea
>> forward.
>
> The tools in bin/ would need a brush through. I.e. throw away the
> unused ones and amend the ones that are used on data/CVE/* to learn
> about the split files.
Oh yes, lots of work remains, whether we keep the history or not. That's
probably the *most* work we need to do.
But before going through that trouble, I think we'd need to get approval
from the security team first, as that's quite a lot of work. I figured
we would make a feasability study first...
a.
--
On reconnait la grandeur et la valeur d'une nation à la façon dont
celle-ci traite ses animaux.
- Mahatma Gandhi
Reply to: