Also found GitExtensions by way of https://stackoverflow.com/questions/10622179/how-to-find-identify-large-files-commits-in-git-history which has a plugin to list large files. It's slow, took about 30 minute on our repo, but looks usable. I don't know if it helps with everyone needing to to do a git reset.
Also note the large jpeg's which have a high number of commits: On Thu, Nov 2, 2017 at 1:23 PM, Terry Brown <[email protected]> wrote: > On Thu, 2 Nov 2017 15:16:58 -0500 > Terry Brown <[email protected]> wrote: > > > I'm not exactly sure how this will impact people who've pulled you > > commits, not the end of world, but there might be an extra step. I'll > > see if I can simulate it and see what happens. > > Hmm, my first impression is that everyone who's pulled those commits > needs to hard reset to, other wise they can get pushed or merged and > pushed again. > > Will check google. > > Cheers -Terry > > -- > You received this message because you are subscribed to the Google Groups > "leo-editor" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/leo-editor. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
