git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Randall S. Becker <rsbecker@nexbridge.com>
Date
Jan 25, 2018, 14:24 UTC
Message-ID
<001101d395e8$31d94430$958bcc90$@nexbridge.com>
In-Reply-To
<e9518459-ebcd-d415-474f-8504472b7a1d@gmail.com>
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.
Previous: Basin IlyaNext: Basin Ilya
Message 2 of 4 in “pushing a delete-only commit consumes too much traffic”
  1. Basin IlyaJan 25, 2018
  2. Randall S. BeckerJan 25, 2018
  3. Basin IlyaJan 25, 2018
  4. Randall S. BeckerJan 26, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.