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

Re: What's cooking in git.git (Aug 2017, #04; Fri, 18)

From
Duy Nguyen <pclouds@gmail.com>
Date
Aug 22, 2017, 08:49 UTC
Message-ID
<CACsJy8AM+dr_in_hW3y6APUo-cKsg+3sAZg9-7+02ZspSZcf=g@mail.gmail.com>
In-Reply-To
<xmqq60dkbma1.fsf@gitster.mtv.corp.google.com>
On Sat, Aug 19, 2017 at 4:26 AM, Junio C Hamano <gitster@pobox.com> wrote:
Show 21 quoted lines
> [Discarded]
>
> * nd/prune-in-worktree (2017-04-24) 12 commits
>  . rev-list: expose and document --single-worktree
>  . revision.c: --reflog add HEAD reflog from all worktrees
>  . files-backend: make reflog iterator go through per-worktree reflog
>  . revision.c: --all adds HEAD from all worktrees
>  . refs: remove dead for_each_*_submodule()
>  . revision.c: use refs_for_each*() instead of for_each_*_submodule()
>  . refs: add refs_head_ref()
>  . refs: move submodule slash stripping code to get_submodule_ref_store
>  . refs.c: refactor get_submodule_ref_store(), share common free block
>  . revision.c: --indexed-objects add objects from all worktrees
>  . revision.c: refactor add_index_objects_to_pending()
>  . revision.h: new flag in struct rev_info wrt. worktree-related refs
>
>  "git gc" and friends when multiple worktrees are used off of a
>  single repository did not consider the index and per-worktree refs
>  of other worktrees as the root for reachability traversal, making
>  objects that are in use only in other worktrees to be subject to
>  garbage collection.

I'm back and will try to continue this. Is it discarded because of lack of progress, or because the problem is already fixed some other way? A quick "git log --oneline" on important files has not revealed anything.

-- 
Duy
Previous: Junio C HamanoNext: Junio C Hamano
Message 9 of 10 in “What's cooking in git.git (Aug 2017, #04; Fri, 18)”
  1. Junio C HamanoAug 18, 2017
  2. Torsten BögershausenAug 19, 2017
  3. Junio C HamanoAug 19, 2017
  4. Jeff KingAug 20, 2017
  5. Jeff KingAug 20, 2017
  6. doc: fix typo in sendemail.identityJeff King, Aug 20, 2017
  7. Martin ÅgrenAug 20, 2017
  8. Junio C HamanoAug 20, 2017
  9. Duy NguyenAug 22, 2017
  10. Junio C HamanoAug 22, 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.