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

Re: [PATCH 0/3] clone: respect configured fetch respecs during initial fetch

From
Jeff King <peff@peff.net>
Date
Nov 15, 2018, 11:08 UTC
Message-ID
<20181115110802.GD19032@sigill.intra.peff.net>
In-Reply-To
<20181114104620.32478-1-szeder.dev@gmail.com>
On Wed, Nov 14, 2018 at 11:46:17AM +0100, SZEDER Gábor wrote:
Show 10 quoted lines
> This patch series should have been marked as v6, but I chose to reset
> the counter, because:
> 
>   - v5 was sent out way over a year ago [1], and surely everybody has
>     forgotten about it since then anyway.  But more importantly:
> 
>   - A lot has happened since then, most notably we now have a refspec
>     API, which makes this patch series much simpler (now it only
>     touches 'builtin/clone.c', the previous version had to add stuff
>     to 'remote.{c,h}' as well).
Thanks for sticking with this!

I skimmed over the old discussion, mostly just to make sure there wasn't anything subtle that might have been forgotten. But nope, all of the subtlety went away because of the refspec API you mentioned.

The whole series looks good to me.
-Peff
Previous: Jeff KingNext: Junio C Hamano
Message 8 of 9 in “clone: respect configured fetch respecs during initial fetch”
  1. 0/3 clone: respect configured fetch respecs during initial fetchSZEDER Gábor, Nov 14, 2018
  2. 1/3 clone: use a more appropriate variable name for the default refspecSZEDER Gábor, Nov 14, 2018
  3. Jeff KingNov 15, 2018
  4. 2/3 clone: respect additional configured fetch refspecs during initial fetchSZEDER Gábor, Nov 14, 2018
  5. Jeff KingNov 15, 2018
  6. 3/3 Documentation/clone: document ignored configuration variablesSZEDER Gábor, Nov 14, 2018
  7. Jeff KingNov 15, 2018
  8. Jeff KingNov 15, 2018
  9. Junio C HamanoNov 16, 2018

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.