From: Basin Ilya <basinilya@gmail.com>
Date: Thu, 25 Jan 2018 15:07:45 GMT
Subject: Re: pushing a delete-only commit consumes too much traffic
Message-ID: <79fd9c0b-3067-afce-1fcd-507b7c97889e@gmail.com>
In-Reply-To: <001101d395e8$31d94430$958bcc90$@nexbridge.com>

> 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 removal.
No




On 25.01.2018 17:24, Randall S. Becker wrote:
> 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 jars previously pushed in a commit that already existed on the upstream? Was the delete an actual removal of history or did you commit with the jars deleted, then pushed? Did you do a merge squash or delete branch to effect the removal. More info please.
> 
> Cheers,
> Randall
> 
> -- Brief whoami:
>   NonStop developer since approximately NonStop(211288444200000000)
>   UNIX developer since approximately 421664400
> -- In my real life, I talk too much.
> 
> 
>