From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: [PATCH] remote-curl: don't pass back fake refs
Date: Mon, 19 Dec 2011 16:12:03 -0500 [thread overview]
Message-ID: <20111219211203.GA18396@sigill.intra.peff.net> (raw)
In-Reply-To: <7vty4wmkdt.fsf@alter.siamese.dyndns.org>
On Mon, Dec 19, 2011 at 11:28:14AM -0800, Junio C Hamano wrote:
> Jeff King <peff@peff.net> writes:
>
> > Perhaps we should squash in the test below, which demonstrates the
> > breakage. I also wonder if this is maint-worthy.
>
> Thanks for a thorough analysis. I agree that this should go to maint even
> more so, as it fixes a case to push to a non-empty repository.
Do you want to squash in those tests, or should I re-send with a commit
message more fully explaining the situation?
-Peff
next prev parent reply other threads:[~2011-12-19 21:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-17 10:45 [PATCH] remote-curl: don't pass back fake refs Jeff King
2011-12-19 17:10 ` Jeff King
2011-12-19 19:28 ` Junio C Hamano
2011-12-19 21:12 ` Jeff King [this message]
2011-12-19 21:28 ` Junio C Hamano
2011-12-19 21:29 ` Jeff King
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=20111219211203.GA18396@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).