From: Mark Jason Dominus <mjd@plover.com>
To: git@vger.kernel.org
Subject: git-push sent too many objects
Date: Tue, 17 Apr 2012 12:53:27 -0400 [thread overview]
Message-ID: <30586.1334681607@plover.com> (raw)
I had a master ref, pointing to commit 231e284, which I branched to
make a "coupon" ref. My remote, "origin" had a copy of commit
231e284.
I modified one file and committed it on "coupon", yielding commit
03b6489. Then I pushed coupon to origin. I expected that git-push
would send about five objects, but instead it reported sending 1,315.
Command output is pasted at http://nopaste.info/a866bb00e0.html .
You can verify that:
1. I pushed only coupon, not any other ref.
2. origin already had a copy of coupon's predecessor commit, 231e284.
3. 03b6489 was identical to 231e284 except for changes in one file.
4. I was not doing anything obviously strange.
What happened here? Why did git-push send 1,315 objects instead of 5?
Mark Jason Dominus mjd@plover.com
next reply other threads:[~2012-04-17 16:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 16:53 Mark Jason Dominus [this message]
2012-04-18 7:59 ` git-push sent too many objects Shawn Pearce
2012-04-18 14:22 ` Mark Jason Dominus
2012-04-26 13:07 ` Jeff King
2012-04-27 0:41 ` Mark Jason Dominus
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=30586.1334681607@plover.com \
--to=mjd@plover.com \
--cc=git@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).