git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2] fetch: don't try to update unfetched tracking refs

From
Jeff King <peff@peff.net>
Date
May 27, 2013, 16:35 UTC
Message-ID
<20130527163500.GA18405@sigill.intra.peff.net>
In-Reply-To
<20130527163308.GO27005@serenity.lan>
On Mon, May 27, 2013 at 05:33:09PM +0100, John Keeping wrote:
Show 7 quoted lines
> > 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
Previous: John Keeping
Message 6 of 6 in “fetch: don't try to update unfetched tracking refs”
  1. fetch: don't try to update unfetched tracking refsJohn Keeping, May 27, 2013
  2. Jeff KingMay 27, 2013
  3. John KeepingMay 27, 2013
  4. Jeff KingMay 27, 2013
  5. fetch: don't try to update unfetched tracking refsJohn Keeping, May 27, 2013
  6. Jeff KingMay 27, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.