Re: [git-sizer] Implications of a large commit object

On Wed, Mar 14, 2018 at 09:33:32AM +0100, Michael Haggerty wrote: > Maybe your migration tool created a huge commit message, for example > listing each of the files that was changed. > > AFAIK this won't cause Git itself any problems, but it's likely to be > inconvenient. For example, when you

Re: [git-sizer] Implications of a large commit object

> On 14 Mar 2018, at 09:33, Michael Haggerty wrote: > > On Wed, Mar 14, 2018 at 9:14 AM, Lars Schneider > wrote: >> I am using Michael's fantastic Git repo analyzer tool "git-sizer" [*] >> and it detected a very large commit of 7.33 MiB in my

Re: [git-sizer] Implications of a large commit object

On Wed, Mar 14, 2018 at 9:14 AM, Lars Schneider wrote: > I am using Michael's fantastic Git repo analyzer tool "git-sizer" [*] > and it detected a very large commit of 7.33 MiB in my repo (see chart > below). > > This large commit is expected. I've imported that repo