From: Jeff King <peff@peff.net>
To: John Keeping <john@keeping.me.uk>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v2] fetch: don't try to update unfetched tracking refs
Date: Mon, 27 May 2013 12:35:00 -0400 [thread overview]
Message-ID: <20130527163500.GA18405@sigill.intra.peff.net> (raw)
In-Reply-To: <20130527163308.GO27005@serenity.lan>
On Mon, May 27, 2013 at 05:33:09PM +0100, John Keeping wrote:
> > Ah, I see. It is not "the refspec on the command-line does not match a
> > configured refspec", but rather "there exists a configured non-pattern
> > refspec that does not match what was on the command-line (even if what
> > was on the command-line did match another refspec)".
>
> Exactly. I've changed the commit message to (hopefully) make this
> clearer.
It does. To me, anyway. :)
Thanks again.
-Peff
prev parent reply other threads:[~2013-05-27 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 11:40 [PATCH] fetch: don't try to update unfetched tracking refs John Keeping
2013-05-27 15:42 ` Jeff King
2013-05-27 16:01 ` John Keeping
2013-05-27 16:19 ` Jeff King
2013-05-27 16:33 ` [PATCH v2] " John Keeping
2013-05-27 16:35 ` Jeff King [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=20130527163500.GA18405@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=john@keeping.me.uk \
/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).