From: Junio C Hamano <gitster@pobox.com>
To: Karthik Nayak <karthik.188@gmail.com>
Cc: Rajiv Sharma <rajiv.tilakraj.sharma@gmail.com>, git@vger.kernel.org
Subject: Re: [BUG] Git push sends too much data unnecessarily
Date: Wed, 14 Jan 2026 09:38:49 -0800 [thread overview]
Message-ID: <xmqqh5sof61i.fsf@gitster.g> (raw)
In-Reply-To: <CAOLa=ZT4fQdHqG+1AeviYuLUR5VG33voJk_DU1y0MzhUKBQvvw@mail.gmail.com> (Karthik Nayak's message of "Wed, 14 Jan 2026 17:27:21 +0100")
Karthik Nayak <karthik.188@gmail.com> writes:
> So it sends all objects required to create the reference, in our case 4
> objects, in your case GBs of data.
"push.negotiate"?
next prev parent reply other threads:[~2026-01-14 17:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 12:41 [BUG] Git push sends too much data unnecessarily Rajiv Sharma
2026-01-14 16:27 ` Karthik Nayak
2026-01-14 17:38 ` Junio C Hamano [this message]
2026-01-14 17:39 ` Rajiv Sharma
2026-01-14 21:11 ` Jeff King
2026-01-14 21:48 ` Rajiv Sharma
2026-01-15 9:43 ` Karthik Nayak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqh5sof61i.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=karthik.188@gmail.com \
--cc=rajiv.tilakraj.sharma@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox