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

Re: [PATCH 2/3] make update-server-info more robust

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 15, 2014, 18:39 UTC
Message-ID
<xmqqlhpk7mpb.fsf@gitster.dls.corp.google.com>
In-Reply-To
<20140913201920.GB27082@peff.net>
Jeff King <peff@peff.net> writes:
Show 6 quoted lines
> Since "git update-server-info" may be called automatically
> as part of a push or a "gc --auto", we should be robust
> against two processes trying to update it simultaneously.
> However, we currently use a fixed tempfile, which means that
> two simultaneous writers may step on each other's toes and
> end up renaming junk into place.

Thanks. I'll queue these clean-ups but we may want to start thinking about deprecating and removing the dumb http support.

Previous: René ScharfeNext: Jeff King
Message 7 of 9 in “repack: call prune_packed_objects() and update_server_info() directly”
  1. repack: call prune_packed_objects() and update_server_info() directlyRené Scharfe, Sep 13, 2014
  2. Stefan BellerSep 13, 2014
  3. Jeff KingSep 13, 2014
  4. 1/3 prune-packed: fix minor memory leakJeff King, Sep 13, 2014
  5. 2/3 make update-server-info more robustJeff King, Sep 13, 2014
  6. René ScharfeSep 14, 2014
  7. Junio C HamanoSep 15, 2014
  8. Jeff KingSep 15, 2014
  9. 3/3 server-info: clean up after writing info/packsJeff King, Sep 13, 2014

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.