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

Re: [PATCH 0/3] nd/multiple-work-trees updates

From
Duy Nguyen <pclouds@gmail.com>
Date
Mar 18, 2015, 08:23 UTC
Message-ID
<CACsJy8Cb1ojc0tS=e4zvy6O=jMVAiVowO6Tp4OWb38_xq3J3HQ@mail.gmail.com>
In-Reply-To
<5509319D.9070109@gmail.com>
On Wed, Mar 18, 2015 at 3:04 PM, Ephrim Khong <dr.khong@gmail.com> wrote:
Show 5 quoted lines
> Without having looked into this and nd/multiple-work-trees, but with "make
> multiple checkouts aware of each other" in mind: Could this mechanism be
> re-used to make alternates aware of each other, to mitigate the dangers of
> having  git gc  on an alternate remove objects that are used by a
> referencing repository?

If we can turn on ref namespace and make $GIT_DIR/config and hooks per worktree, I think it may have a chance of replacing alternate object mechanism entirely: one object database, one ref database (but refs of each worktree is namespaced so no conflicts), multiple worktrees, multiple config files, multiple hooks.

Because some config keys affect object database, having multiple/conflicting config keys imply that this worktree may change object database in a way trhat impacts performance (not correctness) of another worktree. Later on when we have multiple ref backends, if config keys can change ref backend behavior (or even choose the backend), we may run into other problems. This problem might go away if we define that those "global" config keys can't be per-worktree..

In short, I am good at confusing people.
-- 
Duy
Previous: Ephrim Khong
Message 14 of 14 in “nd/multiple-work-trees updates”
  1. 0/3 nd/multiple-work-trees updatesNguyễn Thái Ngọc Duy, Jan 3, 2015
  2. 1/3 checkout: pass whole struct to parse_branchname_arg instead of individual flagsNguyễn Thái Ngọc Duy, Jan 3, 2015
  3. 2/3 checkout: add --ignore-other-wortreesNguyễn Thái Ngọc Duy, Jan 3, 2015
  4. Mark LevedahlJan 5, 2015
  5. 3/3 git-checkout.txt: a note about multiple checkout support for submodulesNguyễn Thái Ngọc Duy, Jan 3, 2015
  6. Mark LevedahlJan 5, 2015
  7. Max KirillovJan 6, 2015
  8. Junio C HamanoFeb 12, 2015
  9. Jens LehmannFeb 12, 2015
  10. Mark LevedahlFeb 13, 2015
  11. Dennis KaarsemakerFeb 13, 2015
  12. Duy NguyenFeb 13, 2015
  13. Ephrim KhongMar 18, 2015
  14. Duy NguyenMar 18, 2015

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.