From: Mark Jason Dominus <mjd@plover.com>
To: Shawn Pearce <spearce@spearce.org>
Cc: Mark Jason Dominus <mjd@plover.com>, git@vger.kernel.org
Subject: Re: git-push sent too many objects
Date: Wed, 18 Apr 2012 10:22:26 -0400 [thread overview]
Message-ID: <15053.1334758946@plover.com> (raw)
In-Reply-To: Your message of "Wed, 18 Apr 2012 00:59:14 PDT." <CAJo=hJuGHymJtZL14mAq0gBZE+za5URoon=rMzPA=tTQC14ftQ@mail.gmail.com>
Shawn Pearce:
> On Tue, Apr 17, 2012 at 09:53, Mark Jason Dominus <mjd@plover.com> wrote:
> > What happened here? =A0Why did git-push send 1,315 objects instead of 5?
>
> Is it possible someone else modified the repository at the same time?
It is extremely unlikely. This repository is controlled by gitolite
and I am the only person who has push access to it. Also, although my
paste doesn't show it, the repository's master reference had not
moved.
I should have mentioned my git version in my original message: it is
1.7.10.rc0.1.g6fd18 .
next prev parent reply other threads:[~2012-04-18 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 16:53 git-push sent too many objects Mark Jason Dominus
2012-04-18 7:59 ` Shawn Pearce
2012-04-18 14:22 ` Mark Jason Dominus [this message]
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=15053.1334758946@plover.com \
--to=mjd@plover.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).