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

Re: [PATCH 0/3] fix unparsed object access in upload-pack

From
René Scharfe <rene.scharfe@lsrfire.ath.cx>
Date
Mar 17, 2013, 16:38 UTC
Message-ID
<5145F1A3.1030906@lsrfire.ath.cx>
In-Reply-To
<20130317054039.GA16070@sigill.intra.peff.net>
Am 17.03.2013 06:40, schrieb Jeff King:
Show 7 quoted lines
> We do have the capability to roll out to one or a few of our servers
> (the granularity is not 0.2%, but it is still small). I'm going to try
> to keep us more in sync with upstream git, but I don't know if I will
> get to the point of ever deploying "master" or "next", even for a small
> portion of the population. We are accumulating more hacks[1] on top of
> git, so it is not just "run master for an hour on this server"; I have
> to actually merge our fork.

Did you perhaps intend to list these hacks in a footnote or link to a repository containing them? (I can't find the counterpart of that [1].)

René
Previous: Jeff King
Message 9 of 9 in “fix unparsed object access in upload-pack”
  1. 0/3 fix unparsed object access in upload-packJeff King, Mar 16, 2013
  2. 1/3 upload-pack: drop lookup-before-parse optimizationJeff King, Mar 16, 2013
  3. 2/3 upload-pack: make sure "want" objects are parsedJeff King, Mar 16, 2013
  4. 3/3 upload-pack: load non-tip "want" objects from diskJeff King, Mar 16, 2013
  5. Junio C HamanoMar 17, 2013
  6. Jeff KingMar 17, 2013
  7. Junio C HamanoMar 17, 2013
  8. Jeff KingMar 17, 2013
  9. René ScharfeMar 17, 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.