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

Re: [PATCH] fetch: document that pruning happens before fetching

From
Duy Nguyen <pclouds@gmail.com>
Date
Jun 14, 2016, 10:36 UTC
Message-ID
<CACsJy8Bbd0=vnbaj4-2m7WKfvWG6PfyXLg1h+970HPsak1hnMQ@mail.gmail.com>
In-Reply-To
<20160614102210.GA14357@sigill.intra.peff.net>
On Tue, Jun 14, 2016 at 5:22 PM, Jeff King <peff@peff.net> wrote:
> I think the documentation should be updated either way. This is not
> about the ordering in the status table, but rather about the order of
> the real operations. The user may care about that ordering if they want
> to know what races are possible
Good point.
> or what would happen if the packfile
> fetch failed (we'd already have deleted the old refs, but wouldn't fetch
> the new ones).

Off topic, but this sounds like a bug to me. We could have kept ref update more consistent (maybe at some point we could even do atomic transaction update for all refs if there's a need for it).

-- 
Duy
Previous: Jeff KingNext: Jeff King
Message 7 of 8 in “fetch: document that pruning happens before fetching”
  1. fetch: document that pruning happens before fetchingJeff King, Jun 13, 2016
  2. Jacob KellerJun 14, 2016
  3. Jeff KingJun 14, 2016
  4. Jacob KellerJun 14, 2016
  5. Duy NguyenJun 14, 2016
  6. Jeff KingJun 14, 2016
  7. Duy NguyenJun 14, 2016
  8. Jeff KingJun 15, 2016

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.