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

Re: What's cooking in git.git (Mar 2017, #05; Mon, 13)

From
JTJonathan Tan <jonathantanmy@google.com>
Date
Mar 14, 2017, 18:17 UTC
Message-ID
<660cc8fe-6386-11e5-8827-8acfe6644397@google.com>
In-Reply-To
<xmqq37egn6fs.fsf@gitster.mtv.corp.google.com>
On 03/13/2017 03:43 PM, Junio C Hamano wrote:
Show 12 quoted lines
> * jt/mark-tree-uninteresting-for-uninteresting-commit (2017-02-28) 3 commits
>  - upload-pack: compute blob reachability correctly
>  - revision: exclude trees/blobs given commit
>  - revision: unify {tree,blob}_objects in rev_info
>
>  The revision/object traversal machinery did not mark all tree and
>  blob objects that are contained in an uninteresting commit as
>  uninteresting, because that is quite costly.  Instead, it only
>  marked those that are contained in an uninteresting boundary commit
>  as uninteresting.
>
>  Retracted?
Yes, this is retracted.
Previous: Junio C Hamano
Message 4 of 4 in “What's cooking in git.git (Mar 2017, #05; Mon, 13)”
  1. Junio C HamanoMar 13, 2017
  2. Stefan BellerMar 13, 2017
  3. Junio C HamanoMar 14, 2017
  4. Jonathan TanMar 14, 2017

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.