RE: pushing a delete-only commit consumes too much traffic

2018-01-25 Thread Randall S. Becker
n Ilya [mailto:basini...@gmail.com] > Sent: January 25, 2018 10:08 AM > To: Randall S. Becker <rsbec...@nexbridge.com>; git@vger.kernel.org > Subject: Re: pushing a delete-only commit consumes too much traffic > > > Were the 60Mb of jars previously pushed in a commit that already ex

Re: pushing a delete-only commit consumes too much traffic

2018-01-25 Thread Basin Ilya
> Were the 60Mb of jars previously pushed in a commit that already existed on > the upstream? yes > Was the delete an actual removal of history or did you commit with the jars > deleted, then pushed? I committed with the jars deleted > Did you do a merge squash or delete branch to effect the

RE: pushing a delete-only commit consumes too much traffic

2018-01-25 Thread Randall S. Becker
On January 25, 2018 9:15 AM, Basin Ilya wrote: > I had a 60Mb worth of unneeded jar files in the project. I created a new > branch and performed `git rm` on them. Now while I was pushing the change > the counter of sent data reached 80Mb. Why is that? Can you provide more info? Were the 60Mb of