git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Jason Dominus <mjd@plover.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: git-push sent too many objects
Date: Thu, 26 Apr 2012 20:41:53 -0400	[thread overview]
Message-ID: <5097.1335487313@plover.com> (raw)
In-Reply-To: Your message of "Thu, 26 Apr 2012 09:07:17 EDT." <20120426130717.GB27785@sigill.intra.peff.net>

Jeff King:
> Is the repository public? I can't reproduce the issue on a trivial test
> case, but it might be possible to create the original state of the
> client and server repos with judicious use of "reset" and "prune".

The repository has been heavily used since I made the report. If I
notice the same behavior againb, I will try to capture the repo state
for investigation.

      reply	other threads:[~2012-04-27  1:42 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
2012-04-26 13:07     ` Jeff King
2012-04-27  0:41       ` Mark Jason Dominus [this message]

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=5097.1335487313@plover.com \
    --to=mjd@plover.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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).